Full Android interception: inject CA cert into system store (root required), set up ADB reverse tunnel, and optionally set Wi-Fi proxy. Proxy must be running.
AI agents invoke interceptor_android_activate 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 performs multiple privileged system-level operations on an Android device: injecting a CA certificate into the system trust store (enabling MITM of TLS traffic), configuring ADB reverse tunnels, and modifying Wi-Fi proxy settings. These are active, side-effecting operations that reconfigure device security settings. Misuse could intercept all device traffic or persist a rogue CA cert.
From the tool's definition inject CA cert into system store (root required), set up ADB reverse tunnel, and optionally set Wi-Fi proxy
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access interceptor_android_activate 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 interceptor_android_activate:
{
"version": "1",
"default": "deny",
"tools": {
"interceptor_android_activate": {
"limits": [
{
"counter": "interceptor_android_activate_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} interceptor_android_activate 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.
Full Android interception: inject CA cert into system store (root required), set up ADB reverse tunnel, and optionally set Wi-Fi proxy. Proxy must be running. 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 interceptor_android_activate: 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.
interceptor_android_activate 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 interceptor_android_activate 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 interceptor_android_activate. 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.
interceptor_android_activate 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.