AI agents use taskPut to create or update resources in Mcp Taskade — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Taskade environment.
This tool modifies data (a task) but does not irreversibly delete or destroy it, nor does it execute arbitrary code or move money. It is a Write operation. Severity is medium because task updates could affect workflow/process integrity depending on the task's importance and whether the agent has legitimate authorization context. Confidence is high because the operation intent is explicit and unambiguous.
From the tool's definition Tool name 'taskPut' and description 'Update task' indicate a reversible modification operation. 'Put' is a standard HTTP/REST verb for updates, and 'Update' explicitly describes the action.
Documented attack patterns abuse exactly the kind of access taskPut gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Taskade, and nothing reaches the server without passing your rules. This is the rule we recommend for taskPut:
{
"version": "1",
"default": "deny",
"tools": {
"taskPut": {
"limits": [
{
"counter": "taskput_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}taskPut 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.
Update task. It is categorised as a Write tool in the Mcp Taskade MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Taskade MCP server in PolicyLayer and add a rule for taskPut: 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 Mcp Taskade. Nothing to install.
taskPut 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 taskPut 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 taskPut. 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.
taskPut is provided by the Mcp Taskade MCP server (taskade/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 57 Mcp Taskade tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
57 Mcp Taskade tools catalogued and risk-classified — across an index of 42,500+ MCP servers.