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 tool adds/creates tasks to a task management system, which modifies data reversibly. This is a Write operation (create). Severity is medium because misuse could create erroneous or spam tasks cluttering the system, but changes are reversible via deletion or editing. Not Execute/Destructive since it only creates, not runs code or deletes data permanently.
From the tool's definition Tool name 'add_task' indicates creation of new task data. Server context describes 'task management capabilities' and 'task tracking', confirming this tool creates or modifies task records. Description is empty, reducing confidence slightly.
Documented attack patterns abuse exactly the kind of access add_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Task Manager MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for add_task:
{
"version": "1",
"default": "deny",
"tools": {
"add_task": {
"limits": [
{
"counter": "add_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_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.
add_task. 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 (tradesdontlie/task-manager-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 Task Manager MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 Task Manager MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.