close_i2c · Buspirate MCP: Risk & Policy

WHAT IT DOES

What close_i2c does on Buspirate

AI agents use close_i2c 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.

WHY IT NEEDS A POLICY

Why close_i2c needs a policy

This tool terminates a session and resets the BusPirate to a safe high-impedance (HiZ) state. It modifies device state reversibly—the session can be reopened by initializing I2C again. This is a safe cleanup operation typical of session-management tools. It does not retrieve data (Read), execute arbitrary code (Execute), delete irreversibly (Destructive), or move money (Financial).

From the tool's definition close_i2c: 'Close an I2C session and reset the BusPirate to HiZ mode.' The tool resets hardware state, explicitly marked [allowed-write], with instant duration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

close_i2c Rate-limited

close_i2c stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "close_i2c": {
      "limits": [
        {
          "counter": "close_i2c_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 close_i2c

What does the close_i2c tool do? +

Close an I2C session and reset the BusPirate to HiZ mode. [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.

How do I enforce a policy on close_i2c? +

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

close_i2c is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit close_i2c? +

Yes. Add a rate_limit block to the close_i2c 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 close_i2c completely? +

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

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