AI agents call read_output to retrieve information from Buspirate without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data from an existing UART session without altering state, executing commands, or affecting hardware. It is a simple data query operation with minimal security risk when used as intended. Severity is low because reading UART output poses no direct harm unless the output itself contains sensitive information, which depends on what the user is monitoring rather than the tool's inherent capabilities.
From the tool's definition Tool name is 'read_output' and description states it 'Read[s] available data from an open UART session.' The verb 'read' and the absence of any modification, deletion, or execution capability indicate a passive data retrieval operation.
Attacks that exploit this kind of access
Read available data from an open UART session. It is categorised as a Read tool in the Buspirate MCP Server, which means it retrieves data without modifying state.
Register the Buspirate MCP server in PolicyLayer and add a rule for read_output: 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 Buspirate. Nothing to install.
read_output 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 read_output 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 read_output. 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.
read_output is provided by the Buspirate MCP server (mplogas/buspirate-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 →