Set the server logging level. Use this tool to control the verbosity of logs generated by the LSP MCP server. Available levels from least to most verbose: emergency, alert, critical, error, warning, notice, info, debug. Increasing verbosity can help troubleshoot issues but may generate large amou...
AI agents use set_log_level to create or update resources in LSP MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LSP MCP Server environment.
set_log_level changes server behavior by adjusting logging verbosity, which is a reversible Write operation. It does not execute arbitrary code, delete data, or trigger external operations—it only modifies a configuration setting. Severity is low because changing log levels has minimal blast radius: it affects only diagnostic output verbosity, not data integrity, access control, or system stability.
From the tool's definition Tool modifies server configuration state via 'Set the server logging level' and accepts parameterized input (log level selection from a fixed set: emergency through debug).
Documented attack patterns abuse exactly the kind of access set_log_level 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 set_log_level:
{
"version": "1",
"default": "deny",
"tools": {
"set_log_level": {
"limits": [
{
"counter": "set_log_level_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_log_level stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Set the server logging level. Use this tool to control the verbosity of logs generated by the LSP MCP server. Available levels from least to most verbose: emergency, alert, critical, error, warning, notice, info, debug. Increasing verbosity can help troubleshoot issues but may generate large amounts of output. It is categorised as a Write tool in the LSP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LSP MCP Server MCP server in PolicyLayer and add a rule for set_log_level: 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.
set_log_level is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_log_level 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 set_log_level. 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.
set_log_level 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.