Update project metadata in the TreeSummary system
AI agents use update_project_metadata 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 data (project metadata) in a reversible manner. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or merely retrieve data (Read). The 'update' operation is characteristic of Write category tools.
From the tool's definition Tool name is 'update_project_metadata' and description states it 'Update project metadata in the TreeSummary system', indicating modification of project metadata records.
Documented attack patterns abuse exactly the kind of access update_project_metadata 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_project_metadata:
{
"version": "1",
"default": "deny",
"tools": {
"update_project_metadata": {
"limits": [
{
"counter": "update_project_metadata_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_project_metadata 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 project metadata in the TreeSummary system. 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_project_metadata: 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_project_metadata 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_project_metadata 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_project_metadata. 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_project_metadata 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.