Chat completion
AI agents invoke openai_chat_completion to trigger actions in Anythingllm. 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 executes an external operation (calling the OpenAI API for chat completion), which may incur costs and involve processing arbitrary input. The description is minimal, lowering confidence slightly, but the name strongly implies an outbound API call.
From the tool's definition Tool name 'openai_chat_completion' and description 'Chat completion' — triggers an external API call to OpenAI to generate a chat completion response.
Attacks that exploit this kind of access
Chat completion. It is categorised as a Execute tool in the Anythingllm MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Anythingllm MCP server in PolicyLayer and add a rule for openai_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 Anythingllm. Nothing to install.
openai_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 openai_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 openai_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.
openai_chat_completion is provided by the Anythingllm MCP server (moliver28/anythingllm-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 →