AI agents use update_metadata to create or update resources in Divide and Conquer MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Divide and Conquer MCP Server environment.
The tool creates or modifies data reversibly by updating task metadata rather than permanently destroying data or executing arbitrary operations. The severity is medium because unintended metadata modifications could disrupt task organization and tracking, but the effects are reversible and limited to metadata fields rather than destructive deletions or financial transactions.
From the tool's definition Tool description states it 'Updates the task metadata,' indicating modification of existing data. The broader server context involves task tracking, context preservation, and progress monitoring with reversible state changes (e.g., mark_task_done,…
Documented attack patterns abuse exactly the kind of access update_metadata gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Divide and Conquer MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_metadata:
{
"version": "1",
"default": "deny",
"tools": {
"update_metadata": {
"limits": [
{
"counter": "update_metadata_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_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.
Updates the task metadata. It is categorised as a Write tool in the Divide and Conquer MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Divide and Conquer MCP Server MCP server in PolicyLayer and add a rule for update_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 Divide and Conquer MCP Server. Nothing to install.
update_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_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_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_metadata is provided by the Divide and Conquer MCP Server MCP server (landicefu/divide-and-conquer-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Divide and Conquer MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 Divide and Conquer MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.