set_location · AVD MCP Server MCP: Risk & Policy

WHAT IT DOES

What set_location does on AVD MCP Server

AI agents invoke set_location to trigger actions in AVD 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 set_location needs a policy

This tool executes an ADB command ('adb emu geo fix') to set the GPS location on the Android emulator. It triggers an external operation that changes device state. It's not purely destructive or financial, but it executes a system-level command with real side effects on the emulator's simulated location.

From the tool's definition Define localização GPS no emulador via adb emu geo fix

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_location Rate-limited

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

FAQ

Questions about set_location

What does the set_location tool do? +

Define localização GPS no emulador via adb emu geo fix. It is categorised as a Execute tool in the AVD 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 set_location? +

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

What risk level is set_location? +

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

Can I rate-limit set_location? +

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

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

set_location is provided by the AVD MCP Server MCP server (jramalho/avd-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.