Update the name, details, and/or completion status of an existing subtask
AI agents use update_subtask to create or update resources in Agentic Tools MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agentic Tools MCP Server environment.
The tool creates or modifies data in a reversible manner without deleting or destroying it. Changes to subtask properties (name, details, completion status) can be undone by subsequent updates. This fits the Write category. Severity is medium because misuse could corrupt project state or workflow, but changes are recoverable and the scope is limited to a single subtask's metadata.
From the tool's definition Tool description states 'Update the name, details, and/or completion status of an existing subtask' — this modifies existing data reversibly (name, details, status can be changed back).
Documented attack patterns abuse exactly the kind of access update_subtask gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agentic Tools MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_subtask:
{
"version": "1",
"default": "deny",
"tools": {
"update_subtask": {
"limits": [
{
"counter": "update_subtask_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_subtask 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 the name, details, and/or completion status of an existing subtask. It is categorised as a Write tool in the Agentic Tools MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agentic Tools MCP Server MCP server in PolicyLayer and add a rule for update_subtask: 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 Agentic Tools MCP Server. Nothing to install.
update_subtask 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_subtask 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_subtask. 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_subtask is provided by the Agentic Tools MCP Server MCP server (pimzino/agentic-tools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 Agentic Tools MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 Agentic Tools MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.