apktool_build
Rebuild an APK from a decoded apktool source directory (closes the patch-and-repack loop with apk_sign).
This record as markdown: /tools/io-github-vmoranv-jshookmcp/apktool-build.md
What apktool_build does on Jshookmcp
AI agents invoke apktool_build to trigger actions in Jshookmcp. 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.
Why apktool_build is rated High
Rebuilding APKs enables arbitrary code injection into mobile applications, critical security risk.
From the tool's definition Rebuild an APK from decoded apktool source directory; modifies Android application package.
Attacks that exploit this kind of access
The rule that runs apktool_build 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 apktool_build, this is the rule to start with:
apktool_build 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every apktool_build call is checked against it from then on.
Questions about apktool_build
Rebuild an APK from a decoded apktool source directory (closes the patch-and-repack loop with apk_sign). It is categorised as a Execute tool in the Jshookmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Jshook MCP server in PolicyLayer and add a rule for apktool_build: 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.
apktool_build 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 apktool_build 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 apktool_build. 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.
apktool_build 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.
Across the catalogue