AI agents use add-task to create or update resources in Akiflow MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Akiflow MCP Server environment.
Creating tasks is reversible (tasks can be deleted or modified later) and has no external side effects beyond the task management system itself. This fits the Write category. Severity is medium because an agent could create numerous tasks or spam the system, causing clutter and confusion, but the impact is limited to the user's own task list and is fully reversible.
From the tool's definition Tool name 'add-task' and description 'Create a new task in Akiflow' indicate data creation. This is a write operation that creates new records in the task management system.
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 Akiflow 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.
Create a new task in Akiflow. It is categorised as a Write tool in the Akiflow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Akiflow 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 Akiflow 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 Akiflow MCP Server MCP server (shrimpwtf/akiflow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Akiflow MCP Server, 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.
22 Akiflow MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.