AI agents invoke chat_completion 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.
Sending a chat completion request executes an LLM inference call on the Ollama server. This is not a simple read (it triggers computation and can produce side effects depending on model/tool use), and it can process arbitrary user-supplied prompts and images.
From the tool's definition 'chat completion API' that 'runs' inference on the Ollama backend, triggering external model execution; supports multimodal inputs including images
Attacks that exploit this kind of access
OpenAI-compatible chat completion API. Supports optional images per message for vision/multimodal models. 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 chat_completion: 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.
chat_completion 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 chat_completion 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 chat_completion. 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.
chat_completion 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 →