AI agents use close_uart to create or update resources in Buspirate — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Buspirate environment.
Closing a UART session and finalizing logs constitutes a reversible write operation—it terminates an active communication channel and commits session data. This is a normal cleanup/teardown action with no destructive or irreversible consequences. The low severity reflects that the primary effect is graceful session termination, which is safe and expected behavior in hardware communication workflows.
From the tool's definition Tool name is 'close_uart' with description 'Close a UART session and finalize logs.' The 'close' operation and 'finalize logs' indicate state modification of an active session, aligned with the [allowed-write] tag in the description.
Attacks that exploit this kind of access
Close a UART session and finalize logs. [allowed-write] [Duration: instant.]. It is categorised as a Write tool in the Buspirate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Buspirate MCP server in PolicyLayer and add a rule for close_uart: 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.
close_uart 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 close_uart 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 close_uart. 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.
close_uart 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 →