Release a claimed task without changing status. Use for explicit handoff or abandonment.
AI agents use release_task to create or update resources in Planning System MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Planning System MCP Server environment.
An AI agent can call release_task faster than any human can review — one bad instruction and it creates or modifies resources in Planning System MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Release a claimed task without changing status. Use for explicit handoff or abandonment. It is categorised as a Write tool in the Planning System MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Planning System MCP Server MCP server in PolicyLayer and add a rule for release_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 Planning System MCP Server. Nothing to install.
release_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 release_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 release_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.
release_task is provided by the Planning System MCP Server MCP server (tagents/agent-planner-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.