AI agents invoke run to trigger actions in Ollama. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers execution of an LLM with user-supplied prompts and parameters. While LLM inference itself is not inherently destructive, the Execute category applies because: (1) it runs external code/models, (2) the output and side-effects are argument-dependent (different prompts yield different results), and (3) in an agentic context, an uncontrolled prompt injection or malicious prompt could cause the model…
From the tool's definition Tool description states it 'Run[s] a model with a prompt' and accepts parameters that control model execution.
Attacks that exploit this kind of access
Run a model with a prompt. Optionally accepts an image file path for vision/multimodal models and a temperature parameter. It is categorised as a Execute tool in the Ollama MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ollama MCP server in PolicyLayer and add a rule for run: 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. Nothing to install.
run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run 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 run. 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.
run is provided by the Ollama MCP server (ollama-mcp-server). 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 →