chat_completion
AI agents invoke chat_completion to trigger actions in Volcengine Knowledge Base 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.
Based on the tool name and server context (knowledge base search and chat functionality for Volcengine), 'chat_completion' likely triggers an LLM chat completion request against external knowledge repositories. This constitutes an external operation/execution rather than a simple read, as it invokes a remote AI service. However, since the description is empty, confidence is reduced.
From the tool's definition Tool name is 'chat_completion'; description is empty and uninformative.
Attacks that exploit this kind of access
chat_completion. It is categorised as a Execute tool in the Volcengine Knowledge Base MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Volcengine Knowledge Base 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 Volcengine Knowledge Base 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 Volcengine Knowledge Base MCP server (suqidan/volcengine_knowledgebase_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 →