Get completion suggestions at a specific location in a file. Use this tool to retrieve code completion options based on the current context, including variable names, function calls, object properties, and more. Helpful for code assistance and auto-completion at a particular location. Use this wh...
AI agents call get_completions to retrieve information from LSP MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries completion metadata from a Language Server Protocol interface. It has no capability to execute code, modify files, delete data, or trigger external operations. The severity is low because misuse would only result in irrelevant code suggestions; an AI agent cannot cause harm by requesting completions.
From the tool's definition Tool description states 'Get completion suggestions' and 'retrieve code completion options' — purely informational operations. No data modification, execution, deletion, or financial transactions occur.
Documented attack patterns abuse exactly the kind of access get_completions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LSP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_completions:
{
"version": "1",
"default": "deny",
"tools": {
"get_completions": {}
}
}get_completions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get completion suggestions at a specific location in a file. Use this tool to retrieve code completion options based on the current context, including variable names, function calls, object properties, and more. Helpful for code assistance and auto-completion at a particular location. Use this when determining which functions you have available in a given package, for example when changing libraries. Requires the file to be opened first. It is categorised as a Read tool in the LSP MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LSP MCP Server MCP server in PolicyLayer and add a rule for get_completions: 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 LSP MCP Server. Nothing to install.
get_completions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_completions 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 get_completions. 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.
get_completions is provided by the LSP MCP Server MCP server (tritlo/lsp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 LSP MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
9 LSP MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.