WRITE. Auto-routes a relevant target into the right section by what it is: an active task goes to
AI agents use relate_task to create or update resources in Agentic Task System — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agentic Task System environment.
This tool creates or modifies task relationships and routing, which is a reversible data modification operation. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read).
From the tool's definition Tool description explicitly states 'WRITE' and describes 'Auto-routes a relevant target into the right section', indicating it modifies task organization/state.
Attacks that exploit this kind of access
WRITE. Auto-routes a relevant target into the right section by what it is: an active task goes to. It is categorised as a Write tool in the Agentic Task System MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agentic Task System MCP server in PolicyLayer and add a rule for relate_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 Agentic Task System. Nothing to install.
relate_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 relate_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 relate_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.
relate_task is provided by the Agentic Task System MCP server (renezander030/agentic-task-system). 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 →