proxy_setup_adb_device
Configure an Android device to use the proxy.
This record as markdown: /tools/io-github-vmoranv-jshookmcp/proxy-setup-adb-device.md
What proxy_setup_adb_device does on Jshookmcp
AI agents use proxy_setup_adb_device to create or update resources in Jshookmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jshookmcp environment.
Why proxy_setup_adb_device is rated Medium
Modifies device network settings reversibly; affects connectivity but not destructive or financial.
From the tool's definition Configure Android device to use the proxy.
Attacks that exploit this kind of access
The rule that runs proxy_setup_adb_device safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For proxy_setup_adb_device, this is the rule to start with:
proxy_setup_adb_device stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every proxy_setup_adb_device call is checked against it from then on.
Questions about proxy_setup_adb_device
Configure an Android device to use the proxy. It is categorised as a Write tool in the Jshookmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jshook MCP server in PolicyLayer and add a rule for proxy_setup_adb_device: 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 Jshookmcp. Nothing to install.
proxy_setup_adb_device is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the proxy_setup_adb_device 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_setup_adb_device. 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_setup_adb_device is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Jshook, and thousands of servers like it.
This server
Across the catalogue