Link an existing resource (text or file) to a task. The resource and task must belong to the same user/project scope. Use this to attach release notes, design docs, references, etc. to one or more tasks. To link a resource to multiple tasks, call this once per task.
AI agents use karea_link_resource_to_task to create or update resources in Karea — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Karea environment.
This tool creates or modifies associations between resources and tasks. While the underlying data (resource and task) are not changed, the tool creates new link relationships in the task management system, which is a form of data modification. This is reversible (links can typically be removed), so it falls under Write rather than Destructive.
From the tool's definition Tool performs linking operation: "Link an existing resource (text or file) to a task" and "attach release notes, design docs, references, etc. to one or more tasks" - these are reversible modifications to task metadata/associations.
Attacks that exploit this kind of access
Link an existing resource (text or file) to a task. The resource and task must belong to the same user/project scope. Use this to attach release notes, design docs, references, etc. to one or more tasks. To link a resource to multiple tasks, call this once per task. It is categorised as a Write tool in the Karea MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Karea MCP server in PolicyLayer and add a rule for karea_link_resource_to_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 Karea. Nothing to install.
karea_link_resource_to_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 karea_link_resource_to_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 karea_link_resource_to_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.
karea_link_resource_to_task is provided by the Karea MCP server (starecz/karea-mcp). 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 →