AI agents use mark_task_done 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 creates or modifies data reversibly by updating the completion status of a checklist item. It does not delete data (ruling out Destructive), does not execute arbitrary code (ruling out Execute), does not move money (ruling out Financial), and performs side effects (ruling out Read). The modification is reversible as indicated by the sibling tool 'mark_task_undone', confirming this is a Write operation.
From the tool's definition Tool marks a checklist item as done, which modifies the state of a task/checklist item in a reversible manner. The description states it 'Marks a checklist item as done', indicating a status update operation.
Documented attack patterns abuse exactly the kind of access mark_task_done 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 mark_task_done:
{
"version": "1",
"default": "deny",
"tools": {
"mark_task_done": {
"limits": [
{
"counter": "mark_task_done_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}mark_task_done 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.
Marks a checklist item as done. 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 mark_task_done: 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.
mark_task_done 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 mark_task_done 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 mark_task_done. 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.
mark_task_done 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.