Add a new task to the task list
AI agents use add_task to create or update resources in Task Manager MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Task Manager MCP Server environment.
The add_task tool creates new data (a task entry) in a persistent store, which is a Write operation. It is reversible via the delete_task tool mentioned as a sibling. The severity is low because task management data typically has minimal blast radius and no external consequences beyond local state changes.
From the tool's definition Tool description states 'Add a new task to the task list' and the server supports 'full CRUD operations including add, list, update, complete, and delete tasks'. Adding a task creates new data reversibly.
Attacks that exploit this kind of access
Add a new task to the task list. It is categorised as a Write tool in the Task Manager MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Task Manager MCP Server MCP server in PolicyLayer and add a rule for add_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 Task Manager MCP Server. Nothing to install.
add_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 add_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 add_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.
add_task is provided by the Task Manager MCP Server MCP server (mylightison/mcp-study). 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 →