AI agents call list_execution_plans to retrieve information from ZMCPTools 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 execution plans for informational purposes (discovery and monitoring). No description suggests it creates, modifies, deletes, or triggers execution of plans—only that it lists them for visibility. This is a read-only operation with no destructive, financial, or execution side effects.
From the tool's definition The tool name is 'list_execution_plans' and the description states it is for 'discovery and monitoring', which indicates retrieval and querying of existing execution plans without modification or side effects.
Documented attack patterns abuse exactly the kind of access list_execution_plans gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ZMCPTools, and nothing reaches the server without passing your rules. This is the rule we recommend for list_execution_plans:
{
"version": "1",
"default": "deny",
"tools": {
"list_execution_plans": {}
}
}list_execution_plans is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List execution plans for discovery and monitoring. It is categorised as a Read tool in the ZMCPTools MCP Server, which means it retrieves data without modifying state.
Register the ZMCPTools MCP server in PolicyLayer and add a rule for list_execution_plans: 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 ZMCPTools. Nothing to install.
list_execution_plans 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_execution_plans 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_execution_plans. 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_execution_plans is provided by the ZMCPTools MCP server (zachhandley/zmcptools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 70 ZMCPTools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
70 ZMCPTools tools catalogued and risk-classified — across an index of 42,500+ MCP servers.