Get full details for a delegation by its library:name.
AI agents call get_delegation to retrieve information from Delegations without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data (delegation details) with no side effects. It is purely a read operation, analogous to 'get' or 'fetch'. There is no code execution, data modification, deletion, or financial impact. The low severity reflects that misuse would only expose information, not cause operational damage.
From the tool's definition Tool name is 'get_delegation' and description states 'Get full details for a delegation by its library:name' — this is a retrieval operation that queries and returns information about a delegation without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Get full details for a delegation by its library:name. It is categorised as a Read tool in the Delegations MCP Server, which means it retrieves data without modifying state.
Register the Delegations MCP server in PolicyLayer and add a rule for get_delegation: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Delegations. Nothing to install.
get_delegation is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_delegation rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_delegation. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_delegation is provided by the Delegations MCP server (kaijfox/delegations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →