Restart the LSP server process. Use this tool to reset the LSP server if it becomes unresponsive, has stale data, or when you need to apply configuration changes. Can optionally reinitialize with a new root directory. Useful for troubleshooting language server issues or when switching projects.
AI agents invoke restart_lsp_server to trigger actions in LSP 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 executes a process restart operation that can trigger external side effects (reinitializing with different root directories, applying configuration changes). While it doesn't irreversibly destroy data (not Destructive) or persistently modify data (not Write), it actively initiates and controls a running process, making it Execute-category.
From the tool's definition Tool restarts an external process (LSP server) with capability to "reinitialize with a new root directory," which constitutes triggering an external operation whose effects depend on arguments and system state.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access restart_lsp_server 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 restart_lsp_server:
{
"version": "1",
"default": "deny",
"tools": {
"restart_lsp_server": {
"limits": [
{
"counter": "restart_lsp_server_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}restart_lsp_server stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Restart the LSP server process. Use this tool to reset the LSP server if it becomes unresponsive, has stale data, or when you need to apply configuration changes. Can optionally reinitialize with a new root directory. Useful for troubleshooting language server issues or when switching projects. It is categorised as a Execute tool in the LSP MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the LSP MCP Server MCP server in PolicyLayer and add a rule for restart_lsp_server: 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.
restart_lsp_server 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 restart_lsp_server 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 restart_lsp_server. 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.
restart_lsp_server 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.