simulate_call · Enhanced ADB MCP Server MCP: Risk & Policy

WHAT IT DOES

What simulate_call does on Enhanced ADB MCP Server

AI agents invoke simulate_call to trigger actions in Enhanced ADB 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 simulate_call needs a policy

This tool triggers an external operation on the device/emulator by simulating an incoming call event. It executes an ADB command to inject a call simulation, which is a side-effectful action that interacts with the Android telephony stack. It's not purely read, and while reversible, it executes a system-level operation rather than writing data.

From the tool's definition Simulate incoming call (emulator only)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

simulate_call Rate-limited

simulate_call 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": {
    "simulate_call": {
      "limits": [
        {
          "counter": "simulate_call_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 Enhanced ADB MCP Server, so you can run agents against it safely.

FAQ

Questions about simulate_call

What does the simulate_call tool do? +

Simulate incoming call (emulator only). It is categorised as a Execute tool in the Enhanced ADB 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 simulate_call? +

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

What risk level is simulate_call? +

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

Can I rate-limit simulate_call? +

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

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

simulate_call is provided by the Enhanced ADB MCP Server MCP server (rahulkr/r_adb_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.