apk_dex_intake
Build a cohesive APK/DEX intake evidence packet: ZIP entries, manifest summary, DEX headers, native libraries, generic surface hints, caller-supplied hint matches, and next actions.
This record as markdown: /tools/io-github-vmoranv-jshookmcp/apk-dex-intake.md
What apk_dex_intake does on Jshookmcp
AI agents call apk_dex_intake 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.
Why apk_dex_intake is rated Low
Tool reads and analyzes APK/DEX file contents without modifying or executing anything.
From the tool's definition Build intake evidence packet: ZIP entries, manifest summary, DEX headers
Attacks that exploit this kind of access
The rule that runs apk_dex_intake 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 apk_dex_intake, this is the rule to start with:
apk_dex_intake is read-only, so it stays allowed. 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 apk_dex_intake call is checked against it from then on.
Questions about apk_dex_intake
Build a cohesive APK/DEX intake evidence packet: ZIP entries, manifest summary, DEX headers, native libraries, generic surface hints, caller-supplied hint matches, and next actions. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.
Register the Jshook MCP server in PolicyLayer and add a rule for apk_dex_intake: 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.
apk_dex_intake is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the apk_dex_intake 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 apk_dex_intake. 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.
apk_dex_intake 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