appstore_build
Build a signed .ipa for TestFlight (auto-detects Flutter/React Native/KMP/Xcode projects).
This record as markdown: /tools/alexgladkov-claude-in-mobile/appstore-build.md
What appstore_build does on Claude Mobile
AI agents invoke appstore_build to trigger actions in Claude Mobile. 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 appstore_build is rated High
This tool executes a complex build pipeline (auto-detecting project types and invoking build systems) whose behavior depends on the repository structure and build configuration. While the output is an app binary rather than direct device manipulation, the process involves running compiler toolchains and code generation operations that are fundamentally Execute-category actions.
From the tool's definition "Build a signed .ipa for TestFlight" — compiles and signs an iOS app binary, executing code generation and cryptographic operations that produce a deployable artifact.
Attacks that exploit this kind of access
The rule that runs appstore_build safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Mobile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For appstore_build, this is the rule to start with:
appstore_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 Claude Mobile, apply this rule, and every appstore_build call is checked against it from then on.
Questions about appstore_build
Build a signed .ipa for TestFlight (auto-detects Flutter/React Native/KMP/Xcode projects). It is categorised as a Execute tool in the Claude Mobile MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Mobile MCP server in PolicyLayer and add a rule for appstore_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 Claude Mobile. Nothing to install.
appstore_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 appstore_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 appstore_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.
appstore_build is provided by the Claude Mobile MCP server (alexgladkov/claude-in-mobile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Mobile, and thousands of servers like it.
Across the catalogue