AI agents call bbs_read_until_nonblank 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.
This tool simply reads and waits for content to appear on a BBS screen buffer—a query operation with no side effects. It retrieves data from the terminal emulator state without creating, modifying, executing, or deleting anything. The read-only nature and lack of any documented mutation or command execution justifies the Read category with low severity.
From the tool's definition Tool name 'bbs_read_until_nonblank' and description 'Read until the screen buffer contains non-whitespace content' indicate passive retrieval of displayed content from a telnet session without modification or execution of commands.
Attacks that exploit this kind of access
Read until the screen buffer contains non-whitespace content. 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 bbs_read_until_nonblank: 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.
bbs_read_until_nonblank 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 bbs_read_until_nonblank 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 bbs_read_until_nonblank. 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.
bbs_read_until_nonblank 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.
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 →