AI agents use update_execution_plan to create or update resources in ZMCPTools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ZMCPTools environment.
This tool creates or modifies plan data reversibly within the orchestration platform. It does not execute external commands, delete data irreversibly, or move finances. The severity is medium because a malformed execution plan could misdirect autonomous agent workflows, causing inefficiency or incorrect task routing, but the effects are generally correctable through subsequent updates.
From the tool's definition Tool name is 'update_execution_plan' and description states 'Update an execution plan', indicating modification of existing plan data.
Documented attack patterns abuse exactly the kind of access update_execution_plan 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 update_execution_plan:
{
"version": "1",
"default": "deny",
"tools": {
"update_execution_plan": {
"limits": [
{
"counter": "update_execution_plan_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_execution_plan stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update an execution plan\. It is categorised as a Write tool in the ZMCPTools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ZMCPTools MCP server in PolicyLayer and add a rule for update_execution_plan: 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.
update_execution_plan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_execution_plan 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 update_execution_plan. 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.
update_execution_plan 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.