spi_transfer · Buspirate MCP: Risk & Policy

WHAT IT DOES

What spi_transfer does on Buspirate

AI agents invoke spi_transfer to trigger actions in Buspirate. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why spi_transfer needs a policy

This tool sends raw SPI transactions to hardware devices, which can trigger arbitrary hardware operations depending on the target device (e.g., writing firmware, modifying flash memory, controlling peripherals). While it has a read-back option, the primary action is executing hardware-level commands whose effects are entirely dependent on the connected device and bytes sent.

From the tool's definition 'Send a raw SPI transaction. Write hex bytes and optionally read back.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

spi_transfer Rate-limited

spi_transfer stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "spi_transfer": {
      "limits": [
        {
          "counter": "spi_transfer_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Buspirate, so you can run agents against it safely.

FAQ

Questions about spi_transfer

What does the spi_transfer tool do? +

Send a raw SPI transaction. Write hex bytes and optionally read back. It is categorised as a Execute tool in the Buspirate MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on spi_transfer? +

Register the Buspirate MCP server in PolicyLayer and add a rule for spi_transfer: 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.

What risk level is spi_transfer? +

spi_transfer is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit spi_transfer? +

Yes. Add a rate_limit block to the spi_transfer 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.

How do I block spi_transfer completely? +

Set action: deny in the PolicyLayer policy for spi_transfer. 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.

What MCP server provides spi_transfer? +

spi_transfer 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.