Tool summarize_ticket

A tool AI agents call, on the MCP server Example Corp assistant.

No approved baseline: nobody approved this tool's scopes.

Says about itself

readOnlyHint: true, openWorldHint: false

Calls

GET /tickets/{id}

Scopes it holds

None

• Warning No scope mapped to this tool

  The mapping gives other tools their scopes, but not this one. Either the tool is not protected, or it uses whatever token the server holds, which is usually the broadest.

  ScopeNeat recommendation: List the scopes this tool's calls require in the mapping.

  Next step: The developer lists the scopes the tool's calls require, and the MCP server owner confirms the mapping.

  Accountable MCP server owner

  Sources: YogaSec practice

  Limit the permissions that LLM tools are granted to other systems to the minimum necessary

  References (2)

  A finding supports evidence for these requirements. On its own it does not make an organization compliant.

  • RTS 2024/1774 Art. 21(d) Related

    a provision on restrictions of access to ICT assets, setting out controls and tools to prevent unauthorised access

    Applies as: legal requirement. Binds the EU financial entities under DORA. Entities under the simplified framework follow Article 33 instead of Article 21.

  • ISO/IEC 27001 A.5.15 Related

    Access control

    Applies as: certifiable standard. Binding only for a certified organization, on the scope of its certificate.

• Warning The tool calls an operation the API description doesn't list

  Only an operation's security requirement says which scopes it needs. For an operation missing from the description, nobody can check that the tool's scopes are the right ones.

  ScopeNeat recommendation: Add the operation to the API description with its security requirement, or fix its name in the tool's calls.

  Next step: The developer documents the operation or fixes the call, and the MCP server owner confirms the tool's calls.

  Accountable MCP server owner

  Sources: YogaSec practice

  the value is a list of scope names required for the execution

  References (1)

  A finding supports evidence for these requirements. On its own it does not make an organization compliant.

  • ISO/IEC 27001 A.5.9 Related

    Inventory of information and other associated assets

    Applies as: certifiable standard. Binding only for a certified organization, on the scope of its certificate.