SHOCK · MCP PiShock Server MCP: Risk & Policy

WHAT IT DOES

What SHOCK does on MCP PiShock Server

AI agents invoke SHOCK 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 SHOCK needs a policy

This tool executes a real-world physical action — delivering an electric shock to a person wearing a PiShock device. Misuse by an AI agent could cause direct physical harm to a human being. It is categorized as Execute (triggering an external physical operation) with critical severity due to the potential for bodily harm.

From the tool's definition Tool name 'SHOCK' on a server described as 'Enables controlling PiShock devices (shock, vibrate, beep)' — directly triggers a physical electric shock on a wearable device with configurable duration and intensity parameters.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

SHOCK Rate-limited

SHOCK 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": {
    "SHOCK": {
      "limits": [
        {
          "counter": "shock_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 SHOCK

What does the SHOCK tool do? +

{"name": "SHOCK", "arguments": {"duration": 2, "intensity": 10}}. 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 SHOCK? +

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

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

Can I rate-limit SHOCK? +

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

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

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