AI agents use reclaim_update_task to create or update resources in Reclaim Ai MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Reclaim Ai MCP Server environment.
The tool updates task records, which creates or modifies data reversibly. This falls under Write category. Severity is medium because task updates can affect workflow and priorities, but changes are reversible (unlike deletion).
From the tool's definition Tool name 'reclaim_update_task' and server description stating the server 'manage[s] Reclaim.ai tasks, including...updating' indicates this tool modifies existing task data.
Documented attack patterns abuse exactly the kind of access reclaim_update_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reclaim Ai MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for reclaim_update_task:
{
"version": "1",
"default": "deny",
"tools": {
"reclaim_update_task": {
"limits": [
{
"counter": "reclaim_update_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}reclaim_update_task stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
reclaim_update_task. It is categorised as a Write tool in the Reclaim Ai MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Reclaim Ai MCP Server MCP server in PolicyLayer and add a rule for reclaim_update_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 Reclaim Ai MCP Server. Nothing to install.
reclaim_update_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 reclaim_update_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 reclaim_update_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.
reclaim_update_task is provided by the Reclaim Ai MCP Server MCP server (johnjhughes/reclaim-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Reclaim Ai MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Reclaim Ai MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.