One-command mobile capture: start explicit + transparent listeners, optionally inject the CA on an Android device, and emit a sudo-runnable script that wires iptables/sysctl/nmcli on the AP iface. Designed to pair with the proxy-ap-card firmware (ESP32-S3 rogue AP over USB-NCM).
AI agents invoke proxy_mobile_setup to trigger actions in Proxy. 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.
This tool executes a complex chain of privileged operations: starting network listeners, injecting certificate authorities onto Android devices (enabling full TLS interception/MITM), running iptables/sysctl/nmcli configuration scripts with sudo, and setting up a rogue access point. The combination of CA injection and rogue AP creation constitutes a powerful MITM attack framework.
From the tool's definition start explicit + transparent listeners, inject the CA on an Android device, emit a sudo-runnable script that wires iptables/sysctl/nmcli on the AP iface, ESP32-S3 rogue AP over USB-NCM
Documented attack patterns abuse exactly the kind of access proxy_mobile_setup gives an agent:
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_setup:
{
"version": "1",
"default": "deny",
"tools": {
"proxy_mobile_setup": {
"limits": [
{
"counter": "proxy_mobile_setup_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}proxy_mobile_setup 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.
Free to start. No card required.
One-command mobile capture: start explicit + transparent listeners, optionally inject the CA on an Android device, and emit a sudo-runnable script that wires iptables/sysctl/nmcli on the AP iface. Designed to pair with the proxy-ap-card firmware (ESP32-S3 rogue AP over USB-NCM). It is categorised as a Execute tool in the Proxy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Proxy MCP server in PolicyLayer and add a rule for proxy_mobile_setup: 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.
proxy_mobile_setup is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the proxy_mobile_setup 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.
Set action: deny in the PolicyLayer policy for proxy_mobile_setup. 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.
proxy_mobile_setup 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.
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.