VIBRATE · MCP PiShock Server MCP: Risk & Policy

WHAT IT DOES

What VIBRATE does on MCP PiShock Server

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

This tool executes a real-world physical action on a PiShock wearable device. While less severe than SHOCK, it still triggers an involuntary physical sensation on a person wearing the device. It is an Execute category action (triggering an external physical operation), with high severity because misuse could cause unwanted physical stimulation to a human.

From the tool's definition Tool name 'VIBRATE' on a server described as 'Enables controlling PiShock devices (shock, vibrate, beep) via the MCP protocol' — directly triggers a physical vibration action on a hardware device.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

VIBRATE Rate-limited

VIBRATE 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": {
    "VIBRATE": {
      "limits": [
        {
          "counter": "vibrate_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 VIBRATE

What does the VIBRATE tool do? +

{"name": "VIBRATE", "arguments": {"duration": 3, "intensity": 50}}. 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 VIBRATE? +

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

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

Can I rate-limit VIBRATE? +

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

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

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