Sends conversational context (messages) to OpenRouter.ai for completion using a specified model. Use this for dialogue, text generation, or instruction-following tasks. Supports advanced provider routing and parameter overrides. Returns the generated text response.
AI agents invoke chat_completion to trigger actions in Openrouterai. 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 API call to OpenRouter.ai, sending arbitrary messages to an AI model and returning generated text. It triggers external computation whose output depends entirely on the arguments passed. While it doesn't directly modify local data or move money, it invokes an external service (which may have associated costs and can produce arbitrary outputs), placing it firmly in Execute.
From the tool's definition Sends conversational context (messages) to OpenRouter.ai for completion using a specified model... triggers external operations whose effects depend on arguments
Attacks that exploit this kind of access
Sends conversational context (messages) to OpenRouter.ai for completion using a specified model. Use this for dialogue, text generation, or instruction-following tasks. Supports advanced provider routing and parameter overrides. Returns the generated text response. It is categorised as a Execute tool in the Openrouterai MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Openrouterai 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 Openrouterai. 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 Openrouterai MCP server (@mcpservers/openrouterai). 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 →