vibrate · Android MCP Server MCP: Risk & Policy

WHAT IT DOES

What vibrate does on Android MCP Server

AI agents invoke vibrate to trigger actions in Android MCP 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 physical action on the Android device (activating the vibration motor). It has no data read/write implications and is not destructive or financial. The blast radius is very low — the worst case is an annoying or unexpected vibration. Classified as Execute because it triggers an external device operation.

From the tool's definition 'Vibrate phone. force=True to vibrate in silent mode.' — triggers a physical hardware action on the 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 Android MCP Server, so you can run agents against it safely.

FAQ

Questions about vibrate

What does the vibrate tool do? +

Vibrate phone. force=True to vibrate in silent mode. It is categorised as a Execute tool in the Android MCP 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 Android MCP 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 Android MCP 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 Android MCP Server MCP server (wujie272/android-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.