AI agents call i2c_read 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 I2C device without modifying state, executing arbitrary code, or causing side effects. It is a query operation on hardware communication bus. While it operates on physical hardware, reading sensor or memory data is fundamentally a Read operation with minimal blast radius—worst case exposes existing data already stored on the device.
From the tool's definition Tool name is 'i2c_read' and description states it 'Read[s] bytes from an I2C device, optionally from a specific register.' The verb 'read' and lack of any modification or execution language clearly indicate data retrieval.
Attacks that exploit this kind of access
Read bytes from an I2C device, optionally from a specific register. 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 i2c_read: 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.
i2c_read 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 i2c_read 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 i2c_read. 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.
i2c_read 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 →