Get code actions for a specific range in a file. Use this tool to obtain available refactorings, quick fixes, and other code modifications that can be applied to a selected code range. Examples include adding imports, fixing errors, or implementing interfaces. Requires the file to be opened first.
AI agents call get_code_actions 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/lists available code actions but does not apply them. It is a query operation that returns what actions are possible, similar to a 'get' or 'list' operation. The actual application of those actions would be a separate step. Severity is low as it only reads metadata about possible code changes.
From the tool's definition Get code actions for a specific range in a file...obtain available refactorings, quick fixes, and other code modifications that can be applied
Documented attack patterns abuse exactly the kind of access get_code_actions 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_code_actions:
{
"version": "1",
"default": "deny",
"tools": {
"get_code_actions": {}
}
}get_code_actions 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 code actions for a specific range in a file. Use this tool to obtain available refactorings, quick fixes, and other code modifications that can be applied to a selected code range. Examples include adding imports, fixing errors, or implementing interfaces. 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_code_actions: 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_code_actions 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_code_actions 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_code_actions. 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_code_actions 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.