List supported programming languages for debugging.
AI agents call debug_list_languages to retrieve information from Polybugger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool simply lists or enumerates supported languages—a read-only informational query. It does not modify state, execute code, attach debuggers, create sessions, or perform any operations that would affect running processes or data. The blast radius of misuse is negligible.
From the tool's definition Tool name 'debug_list_languages' and description 'List supported programming languages for debugging' indicate a retrieval operation that queries static metadata about supported languages with no side effects.
Attacks that exploit this kind of access
List supported programming languages for debugging. It is categorised as a Read tool in the Polybugger MCP Server, which means it retrieves data without modifying state.
Register the Polybugger MCP server in PolicyLayer and add a rule for debug_list_languages: 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 Polybugger. Nothing to install.
debug_list_languages 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 debug_list_languages 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 debug_list_languages. 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.
debug_list_languages is provided by the Polybugger MCP server (wilfoa/polybugger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →