AI agents call list_directives to retrieve information from ATMcp 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 directives with optional filtering by role (sent/received). It has no side effects, does not execute code or commands, does not modify data, and does not delete or move resources. It is a straightforward read operation that returns information about directives in a multi-agent task management system.
From the tool's definition Tool name 'list_directives' and description 'List directives' with filtering by role parameter indicates data retrieval only. The action is query-based ('list') with no modification, creation, deletion, or execution capability.
Attacks that exploit this kind of access
List directives. role='sent' (issued by you), 'received' (addressed to you), or omit. It is categorised as a Read tool in the ATMcp MCP Server, which means it retrieves data without modifying state.
Register the AT MCP server in PolicyLayer and add a rule for list_directives: 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 ATMcp. Nothing to install.
list_directives 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_directives 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_directives. 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_directives is provided by the AT MCP server (midcheck/atmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
list_directives is one line of AT's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →