WRITE. Adds a resource the task consults (an external URL or a reference note) to its
AI agents use add_task_reference 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 data reversibly by appending resource references (URLs or notes) to a task. It does not delete, execute code, move money, or trigger external operations—it simply adds metadata to an existing task. This is a classic Write operation with low severity since the blast radius of adding incorrect references is minimal and easily corrected.
From the tool's definition Tool name 'add_task_reference' and description explicitly states 'WRITE. Adds a resource' indicating it modifies task data by adding references/URLs.
Attacks that exploit this kind of access
WRITE. Adds a resource the task consults (an external URL or a reference note) to its. 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 add_task_reference: 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.
add_task_reference 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 add_task_reference 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 add_task_reference. 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.
add_task_reference 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 →