BEEP · MCP PiShock Server MCP: Risk & Policy

WHAT IT DOES

What BEEP does on MCP PiShock Server

AI agents invoke BEEP to trigger actions in MCP PiShock Server. 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 BEEP needs a policy

BEEP triggers an external operation on a physical PiShock device. It is not purely a data read or write, but an execution of a hardware command. While less harmful than SHOCK, it still causes a real-world physical effect on a device (and potentially on a person wearing it).

From the tool's definition Tool name 'BEEP' on a server that 'Enables controlling PiShock devices (shock, vibrate, beep) via the MCP protocol' — triggers a physical beep action on an external hardware device.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

BEEP Rate-limited

BEEP 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": {
    "BEEP": {
      "limits": [
        {
          "counter": "beep_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 MCP PiShock Server, so you can run agents against it safely.

FAQ

Questions about BEEP

What does the BEEP tool do? +

{"name": "BEEP", "arguments": {"duration": 1}}. It is categorised as a Execute tool in the MCP PiShock Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on BEEP? +

Register the MCP PiShock Server MCP server in PolicyLayer and add a rule for BEEP: 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 MCP PiShock Server. Nothing to install.

What risk level is BEEP? +

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

Can I rate-limit BEEP? +

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

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

BEEP is provided by the MCP PiShock Server MCP server (kyrnepi/mcp-pishock-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.