AI agents use add-task to create or update resources in Ollama MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ollama MCP Server environment.
This tool creates new data (tasks) in a workflow management system, which is a reversible Write operation. Severity is medium because misuse could clutter the task queue or create spurious tasks that consume resources, but the operation is not destructive and does not execute arbitrary code or move funds.
From the tool's definition Tool name 'add-task' and description 'Add a new task' indicate data creation. The context of an Ollama MCP Server managing 'task decomposition, evaluation, and workflow management' confirms this creates new task records in a workflow 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 Ollama 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 a new task. It is categorised as a Write tool in the Ollama MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ollama 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 Ollama 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 Ollama MCP Server MCP server (newaitees/ollama-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ollama 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.
4 Ollama MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.