AI agents invoke adb_install to trigger actions in Claude Pascal MCP Server. 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.
Based on the tool name and server context, adb_install almost certainly installs an APK or package onto an Android device via ADB (Android Debug Bridge). Installing software on a device is an Execute-level action with high blast radius — a malicious or unintended APK installation could compromise the device. The empty description lowers confidence slightly, but the name is strongly indicative.
From the tool's definition Tool name 'adb_install' on a server that interacts with Android devices via ADB; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access adb_install gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Pascal MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for adb_install:
{
"version": "1",
"default": "deny",
"tools": {
"adb_install": {
"limits": [
{
"counter": "adb_install_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}adb_install 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.
adb_install. It is categorised as a Execute tool in the Claude Pascal MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Pascal MCP Server MCP server in PolicyLayer and add a rule for adb_install: 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 Claude Pascal MCP Server. Nothing to install.
adb_install 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 adb_install 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 adb_install. 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.
adb_install is provided by the Claude Pascal MCP Server MCP server (tina4stack/claude-pascal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Pascal MCP Server, 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.
53 Claude Pascal MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.