Critical Risk →

rm

Remove a model

How to control rm ↓

AI agents call rm 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

The tool performs an irreversible deletion operation (rm is the standard Unix command for permanent file/resource removal). Once a model is removed, it cannot be recovered without re-downloading or re-importing it. This constitutes a destructive action with no undo capability.

From the tool's definition Tool name 'rm' and description 'Remove a model' directly indicate irreversible deletion of a model resource from the Ollama system.

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

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

rm 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 rm tool do? +

Remove a model. 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 rm? +

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

rm 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 rm? +

Yes. Add a rate_limit block to the rm 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 rm completely? +

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

rm is provided by the Ollama MCP Server MCP server (nighttrek/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 10 Ollama MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

10 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.