proxy_mobile_detect_iface

THE RISK

Low Risk

Why proxy_mobile_detect_iface needs a policy

The tool performs network interface detection/enumeration, retrieving information about available USB-NCM interfaces. This is a read-only operation that gathers system state information without side effects, modifications, or command execution. While it relates to proxy infrastructure, it is fundamentally a querying operation.

From the tool's definition 'Auto-detect the USB-NCM interface' and 'Returns null + iface list if none found' — this tool queries/detects device interfaces without modifying, deleting, or executing commands.

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

POLICY

How to control proxy_mobile_detect_iface

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 proxy_mobile_detect_iface:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "proxy_mobile_detect_iface": {}
  }
}

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Proxy tools

Destructive interceptor_docker_detach Remove proxy configuration from a Docker container and clean up injected files. Destructive proxy_clear_traffic Clear all captured traffic from the buffer. Destructive proxy_delete_session Delete a recorded session from disk. Destructive proxy_remove_host_upstream Remove a per-host upstream proxy override. Destructive proxy_remove_rule Delete an interception rule. Destructive proxy_session_stop Stop persistent on-disk capture and finalize the active session. Destructive interceptor_deactivate_all Kill ALL active interceptors across all types. Emergency cleanup — stops all browser insta Destructive interceptor_kill Kill a spawned process by target ID. Also retrieves final stdout/stderr output.

All 89 Proxy tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about proxy_mobile_detect_iface

What does the proxy_mobile_detect_iface tool do? +

Auto-detect the USB-NCM interface the proxy-ap-card presents as (via the cdc_ncm driver). Returns null + iface list if none found. 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 proxy_mobile_detect_iface? +

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

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

Can I rate-limit proxy_mobile_detect_iface? +

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

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

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

CHECK YOUR STACK →