AI agents invoke completion to trigger actions in Symbols. 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.
completion triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
Get context-aware code completions at a precise file position. For the best results, place the cursor immediately after the trigger point, for example right after. It is categorised as a Execute tool in the Symbols MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Symbols MCP server in PolicyLayer and add a rule for 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 Symbols. Nothing to install.
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 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 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.
completion is provided by the Symbols MCP server (@p1va/symbols). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.