OpenAI-compatible chat completion API
AI agents invoke ollama_chat_completion to trigger actions in Unified MCP Server. 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.
Chat completion invokes an LLM to generate responses based on input messages. This is an external operation whose effects depend on the arguments passed (the conversation content and model chosen). It is not a simple read of stored data; it executes a model inference process. Given the server also hosts code generation, analysis, and debugging tools, misuse could produce harmful code or content.
From the tool's definition 'chat completion API' — triggers inference on a local LLM via Ollama, executing model computation with arbitrary user-supplied messages
Attacks that exploit this kind of access
OpenAI-compatible chat completion API. It is categorised as a Execute tool in the Unified MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Unified MCP Server MCP server in PolicyLayer and add a rule for ollama_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 Unified MCP Server. Nothing to install.
ollama_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 ollama_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 ollama_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.
ollama_chat_completion is provided by the Unified MCP Server MCP server (qingyunyupan/ollama-mcp). 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 →