AI agents call debug_screen to retrieve information from Mcp Bbs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears designed to inspect or dump screen contents for troubleshooting, which is a read operation. However, confidence is moderate (0.7) because the description is empty, leaving room for uncertainty about whether it might have side effects (e.g., capturing sensitive user data, triggering logs, or interacting with the BBS session in unexpected ways).
From the tool's definition Tool name 'debug_screen' suggests reading/inspection of screen state. Given context of a BBS telnet client with 'ANSI terminal emulation' and 'pattern-based screen reading', this tool likely retrieves current display buffer or terminal state for debugging…
Attacks that exploit this kind of access
debug_screen. It is categorised as a Read tool in the Mcp Bbs MCP Server, which means it retrieves data without modifying state.
Register the Mcp Bbs MCP server in PolicyLayer and add a rule for debug_screen: 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 Mcp Bbs. Nothing to install.
debug_screen 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_screen 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_screen. 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_screen is provided by the Mcp Bbs MCP server (livingstaccato/mcp-bbs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
debug_screen is one line of Mcp Bbs's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →