AI agents use create_task to create or update resources in Todo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todo environment.
Creating a task in a To Do list is a write operation that adds data to a user's task management system. It is reversible (tasks can be deleted or modified), so it does not qualify as Destructive. It involves no code execution, data retrieval only, or financial impact. The severity is low because misuse would only result in unwanted tasks being added to the user's list, with no cascading or critical impact.
From the tool's definition Tool description states it 'Create a new task' which is a create operation that modifies data reversibly. The note about recurrence constraints does not change the fundamental nature of the operation—tasks can be updated or deleted afterward.
Attacks that exploit this kind of access
Create a new task in a To Do list. Note: recurrence can only be set at creation time, not updated later. It is categorised as a Write tool in the Todo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todo MCP server in PolicyLayer and add a rule for create_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 Todo. Nothing to install.
create_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 create_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 create_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.
create_task is provided by the Todo MCP server (jc1122/todo-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 →