Critical Risk →

ollama_delete

Delete a model from local storage. Removes the model and frees up disk space.

How to control ollama_delete ↓

AI agents call ollama_delete to permanently remove resources in Ollama MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

This tool performs an irreversible deletion operation on stored model data. Once a model is deleted from local storage, it is gone unless the user re-downloads or rebuilds it.

From the tool's definition 'Delete a model from local storage. Removes the model and frees up disk space.' - the tool irreversibly removes data (a model) that cannot be recovered without re-downloading or re-creating it.

Documented attack patterns abuse exactly the kind of access ollama_delete 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 ollama_delete:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "ollama_delete"
  ]
}

ollama_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Ollama MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the ollama_delete tool do? +

Delete a model from local storage. Removes the model and frees up disk space. It is categorised as a Destructive tool in the Ollama MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on ollama_delete? +

Register the Ollama MCP Server MCP server in PolicyLayer and add a rule for ollama_delete: 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.

What risk level is ollama_delete? +

ollama_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit ollama_delete? +

Yes. Add a rate_limit block to the ollama_delete 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.

How do I block ollama_delete completely? +

Set action: deny in the PolicyLayer policy for ollama_delete. 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.

What MCP server provides ollama_delete? +

ollama_delete is provided by the Ollama MCP Server MCP server (rawveg/ollama-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ollama MCP Server tool call.

Deterministic rules across all 13 Ollama MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

13 Ollama MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.