Mark a running task as completed. Optionally append a new run context snapshot. Pass clientToken to make retries idempotent.
AI agents use complete_task to create or update resources in State Trace — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your State Trace environment.
This tool modifies the state of a task by changing its status from running to completed and may add new context snapshots. These are Write operations (state changes that can be reversed or corrected) rather than Destructive ones.
From the tool's definition Tool description states "Mark a running task as completed. Optionally append a new run context snapshot." The action of marking a task complete and appending snapshots are reversible state modifications.
Attacks that exploit this kind of access
Mark a running task as completed. Optionally append a new run context snapshot. Pass clientToken to make retries idempotent. It is categorised as a Write tool in the State Trace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the State Trace MCP server in PolicyLayer and add a rule for complete_task: 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 State Trace. Nothing to install.
complete_task 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 complete_task 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 complete_task. 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.
complete_task is provided by the State Trace MCP server (agent-pattern-labs/state-trace). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →