Update an existing task. When users provide natural language with time/date references, convert them to Super Productivity syntax in the title field.
AI agents use update_task to create or update resources in SP-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SP-MCP environment.
This tool creates or modifies data reversibly—it updates task properties without permanently deleting them. The changes can be undone or modified again by subsequent updates. While it affects task state, the modifications are not irreversible. This fits the Write category.
From the tool's definition Tool name is 'update_task' and description states 'Update an existing task', which modifies existing data in the task management system.
Documented attack patterns abuse exactly the kind of access update_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SP-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for update_task:
{
"version": "1",
"default": "deny",
"tools": {
"update_task": {
"limits": [
{
"counter": "update_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Update an existing task. When users provide natural language with time/date references, convert them to Super Productivity syntax in the title field. It is categorised as a Write tool in the SP-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SP- MCP server in PolicyLayer and add a rule for 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 SP-MCP. Nothing to install.
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 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 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.
update_task is provided by the SP- MCP server (organicmoron/sp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 SP-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 SP-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.