智能补全未完成的代码,根据上下文和代码意图生成后续代码。适用于函数补全、逻辑补全等场景。
AI agents invoke code_complete to trigger actions in Unified 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.
This tool generates code completions, which is primarily a Write/Read operation producing code artifacts. However, given that it generates executable code and is part of a server with code execution siblings (code_generate, code_debug, code_test_generate), the generated code could be executed in downstream steps. The tool itself appears to generate/write code rather than execute it, placing it at Write level.
From the tool's definition 智能补全未完成的代码,根据上下文和代码意图生成后续代码 (intelligently completes unfinished code, generates subsequent code based on context and intent)
Attacks that exploit this kind of access
智能补全未完成的代码,根据上下文和代码意图生成后续代码。适用于函数补全、逻辑补全等场景。. It is categorised as a Execute tool in the Unified MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Unified MCP Server MCP server in PolicyLayer and add a rule for code_complete: 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 Unified MCP Server. Nothing to install.
code_complete 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 code_complete 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 code_complete. 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.
code_complete is provided by the Unified MCP Server MCP server (qingyunyupan/ollama-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 →