AI agents call spi_probe 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.
The spi_probe tool performs a non-destructive query of hardware state and identification data from an SPI device. It retrieves manufacturer/device identification and status information without modifying device state, executing code, or triggering external operations. This is a pure read operation with minimal security risk unless the information disclosed could be sensitive in a specific threat model.
From the tool's definition Tool description states 'Read JEDEC ID and status register from an SPI flash chip' — explicitly a read operation with no modification or execution of code.
Attacks that exploit this kind of access
Read JEDEC ID and status register from an SPI flash chip. 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 spi_probe: 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.
spi_probe 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 spi_probe 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 spi_probe. 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.
spi_probe 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 →