AI agents use enable_bundle_capability to create or update resources in App Store Connect — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your App Store Connect environment.
This tool creates or modifies app configuration state (bundle capabilities) within Apple's App Store Connect. While reversible (a capability can be disabled), enabling capabilities affects app permissions and features, which could have significant security and functional implications for an iOS app.
From the tool's definition Tool name is 'enable_bundle_capability' and description states 'Enable a capability for a bundle ID'. This modifies the configuration of an app bundle by adding/activating a capability, which is a reversible configuration change.
Documented attack patterns abuse exactly the kind of access enable_bundle_capability gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and App Store Connect, and nothing reaches the server without passing your rules. This is the rule we recommend for enable_bundle_capability:
{
"version": "1",
"default": "deny",
"tools": {
"enable_bundle_capability": {
"limits": [
{
"counter": "enable_bundle_capability_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}enable_bundle_capability stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Enable a capability for a bundle ID. It is categorised as a Write tool in the App Store Connect MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the App Store Connect MCP server in PolicyLayer and add a rule for enable_bundle_capability: 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 App Store Connect. Nothing to install.
enable_bundle_capability is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the enable_bundle_capability 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 enable_bundle_capability. 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.
enable_bundle_capability is provided by the App Store Connect MCP server (joshuarileydev/app-store-connect-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from App Store Connect, 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.
27 App Store Connect tools catalogued and risk-classified — across an index of 43,000+ MCP servers.