openai_chat_completion
AI agents invoke openai_chat_completion to trigger actions in API Tester 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.
The tool name strongly implies it triggers an OpenAI Chat Completion API call, which executes an external LLM operation using stored credentials. This is an Execute-category action (triggering external operations). The description is empty, lowering confidence, but the server context and sibling tools confirm API execution behavior.
From the tool's definition Tool name 'openai_chat_completion' on a server described as making API requests and OpenAI integrations on the user's behalf.
Attacks that exploit this kind of access
openai_chat_completion. It is categorised as a Execute tool in the API Tester MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the API Tester MCP Server 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 API Tester MCP Server. 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 API Tester MCP Server MCP server (vikrant-khedkar/api-tester-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 →