chat_completion
AI agents invoke chat_completion to trigger actions in LMStudio-MCP. 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 tools typically send prompts to an LLM and return generated responses, constituting an external operation (triggering inference on a local LLM). This falls under Execute as it triggers an external operation whose effects depend on arguments. Severity is high because an AI agent could use this to chain prompts to another LLM in potentially uncontrolled ways (prompt injection, recursive calls).
From the tool's definition Tool name 'chat_completion' on a server described as allowing Claude to communicate with locally running LLM models via LM Studio; description is empty/uninformative.
Attacks that exploit this kind of access
chat_completion. It is categorised as a Execute tool in the LMStudio-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the LMStudio- 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 LMStudio-MCP. 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 LMStudio- MCP server (samscarrow/lmstudio-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 →