AI agents use taskPutDate 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 task metadata (a date field) in a reversible manner. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely retrieve information (Read). The ability to update dates on tasks could affect scheduling or workflow if misused by an agent, but changes are non-destructive and can be corrected.
From the tool's definition Tool name 'taskPutDate' and description 'Create or update date for a task' indicate reversible modification of task data. The verbs 'create' and 'update' are characteristic of Write operations.
Documented attack patterns abuse exactly the kind of access taskPutDate 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 taskPutDate:
{
"version": "1",
"default": "deny",
"tools": {
"taskPutDate": {
"limits": [
{
"counter": "taskputdate_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}taskPutDate 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.
Create or update date for a 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 taskPutDate: 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.
taskPutDate 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 taskPutDate 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 taskPutDate. 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.
taskPutDate 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.