List all available delegations. Also refreshes the registry from disk.
AI agents call list_delegations 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 performs a query operation to enumerate available delegations and refresh metadata from disk. While it includes a refresh component, that is a cache/state synchronization operation, not a modification of user data or system configuration. The primary function is information retrieval, making this a Read category tool with low severity.
From the tool's definition Tool name is 'list_delegations' and description states 'List all available delegations. Also refreshes the registry from disk.' The verb 'list' is a read operation that retrieves and enumerates data without modifying it.
Attacks that exploit this kind of access
List all available delegations. Also refreshes the registry from disk. 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 list_delegations: 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.
list_delegations 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 list_delegations 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 list_delegations. 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.
list_delegations 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 →