adb_pull_native_libs

Pull native shared libraries (.so) for an installed app from a device.

SERVERJshookmcp SOURCE@jshookmcp/jshook

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/adb-pull-native-libs.md

WHAT IT DOES

What adb_pull_native_libs does on Jshookmcp

AI agents call adb_pull_native_libs to retrieve information from Jshookmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why adb_pull_native_libs is rated Low

Retrieves binary libraries from device with no side effects, but sensitive proprietary code exposure.

From the tool's definition Pull native shared libraries (.so) for installed app from device.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adb_pull_native_libs 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 adb_pull_native_libs, this is the rule to start with:

adb_pull_native_libs Allowed

adb_pull_native_libs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every adb_pull_native_libs call is checked against it from then on.

FAQ

Questions about adb_pull_native_libs

What does the adb_pull_native_libs tool do? +

Pull native shared libraries (.so) for an installed app from a device. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on adb_pull_native_libs? +

Register the Jshook MCP server in PolicyLayer and add a rule for adb_pull_native_libs: 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.

What risk level is adb_pull_native_libs? +

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

Can I rate-limit adb_pull_native_libs? +

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

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

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

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →