Download a model from the Ollama library to the local machine.
AI agents use ollama_pull_model to create or update resources in Ollama-Omega — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ollama-Omega environment.
This tool writes data to the local machine by downloading a model. It creates new files on disk but does not execute code, delete data, or involve financial transactions. Misuse could involve pulling large or malicious models, consuming significant disk space and bandwidth, hence medium severity.
From the tool's definition Download a model from the Ollama library to the local machine
Attacks that exploit this kind of access
Download a model from the Ollama library to the local machine. It is categorised as a Write tool in the Ollama-Omega MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ollama-Omega MCP server in PolicyLayer and add a rule for ollama_pull_model: 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-Omega. Nothing to install.
ollama_pull_model 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 ollama_pull_model 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 ollama_pull_model. 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.
ollama_pull_model is provided by the Ollama-Omega MCP server (vrtxomega/ollama-omega). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →