AI agents use task_update to create or update resources in Scopecraft Command — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Scopecraft Command environment.
The task_update tool modifies existing task data within the MDTM system. This is a reversible operation (the previous state can be restored through another update), distinguishing it from destructive operations. The blast radius is moderate—a misdirected or erroneous update could corrupt task metadata or workflow state, but the effect is limited to individual or related tasks and is recoverable.
From the tool's definition The tool name is 'task_update' and description states it 'Updates a task', which is a modification operation that creates or modifies data reversibly. This aligns with the Write category definition of actions that create or modify data.
Documented attack patterns abuse exactly the kind of access task_update gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Scopecraft Command, and nothing reaches the server without passing your rules. This is the rule we recommend for task_update:
{
"version": "1",
"default": "deny",
"tools": {
"task_update": {
"limits": [
{
"counter": "task_update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}task_update 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 a task. It is categorised as a Write tool in the Scopecraft Command MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Scopecraft Command MCP server in PolicyLayer and add a rule for task_update: 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 Scopecraft Command. Nothing to install.
task_update 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 task_update 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 task_update. 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.
task_update is provided by the Scopecraft Command MCP server (scopecraft/command). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 Scopecraft Command tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
18 Scopecraft Command tools catalogued and risk-classified — across an index of 42,500+ MCP servers.