Low Risk

interceptor_android_devices

List connected Android devices via ADB with model, version, root status, and whether they

How to control interceptor_android_devices ↓

What interceptor_android_devices does on Proxy

AI agents call interceptor_android_devices to retrieve information from Proxy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why interceptor_android_devices needs a policy

This tool queries and returns information about connected Android devices without making any changes to them or executing operations. It is purely informational/diagnostic, making it a Read operation with low severity. The potential for misuse is minimal as it only exposes metadata about devices already under the operator's control.

From the tool's definition Tool name contains 'list' action (implied by 'List connected Android devices'); description states it retrieves device information: 'model, version, root status' with no mention of modification, deletion, or execution of commands on those devices.

Risk signalsAdmin/system-level operation

Documented attack patterns abuse exactly the kind of access interceptor_android_devices gives an agent:

How to control interceptor_android_devices

PolicyLayer is an MCP gateway — it sits between your AI agents and Proxy, and nothing reaches the server without passing your rules. This is the rule we recommend for interceptor_android_devices:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "interceptor_android_devices": {}
  }
}

interceptor_android_devices is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Proxy — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about interceptor_android_devices

What does the interceptor_android_devices tool do? +

List connected Android devices via ADB with model, version, root status, and whether they. It is categorised as a Read tool in the Proxy MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on interceptor_android_devices? +

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

What risk level is interceptor_android_devices? +

interceptor_android_devices is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit interceptor_android_devices? +

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

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

interceptor_android_devices is provided by the Proxy MCP server (yfe404/proxy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Proxy tool call.

Start from Proxy, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

89 Proxy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.