AI agents use add_resource 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.
This tool modifies task state by adding resources, which is a reversible operation (resources can be removed). While it affects task data, the operation has limited blast radius—it does not execute code, delete data, or cause financial harm. The context of a task management/divide-and-conquer system suggests resources are metadata or references added to tasks, making this a straightforward Write operation.
From the tool's definition The tool 'add_resource' adds a resource to a task, which creates or modifies data in a reversible manner. The description indicates it performs a create/write operation within the task management system.
Documented attack patterns abuse exactly the kind of access add_resource 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 add_resource:
{
"version": "1",
"default": "deny",
"tools": {
"add_resource": {
"limits": [
{
"counter": "add_resource_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_resource 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.
Adds a resource to the task. 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 add_resource: 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.
add_resource 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 add_resource 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 add_resource. 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.
add_resource 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.