AI agents use add_task to create or update resources in MCP Personal Assistant Agent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Personal Assistant Agent environment.
This tool creates a new task record, which is a write operation that modifies the task list state. It has no side effects beyond data creation and is easily reversible, making it Write category with low severity. The blast radius is minimal—a malicious agent could spam tasks, but damage is contained and easily cleaned up.
From the tool's definition Tool name 'add_task' and description 'Add a new task' indicate creation of new data. The action is reversible (tasks can be deleted via the sibling tool 'delete_task').
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 MCP Personal Assistant Agent, 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 a new task. It is categorised as a Write tool in the MCP Personal Assistant Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Personal Assistant Agent 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 MCP Personal Assistant Agent. 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 MCP Personal Assistant Agent MCP server (zhangzhongnan928/mcp-pa-ai-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Personal Assistant Agent, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
19 MCP Personal Assistant Agent tools catalogued and risk-classified — across an index of 43,000+ MCP servers.