disable_bundle_capability

THE RISK

Medium Risk

Why disable_bundle_capability needs a policy

This is a Write operation because it modifies app configuration reversibly—a capability can be re-enabled. However, it scores high severity because disabling bundle capabilities could break app functionality, require re-signing, trigger app review delays, or prevent the app from operating correctly if critical capabilities are disabled.

From the tool's definition The tool 'disable_bundle_capability' modifies bundle configuration by removing/disabling a capability, which is a reversible change to app settings in App Store Connect.

Documented attack patterns abuse exactly the kind of access disable_bundle_capability gives an agent:

POLICY

How to control disable_bundle_capability

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 disable_bundle_capability:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "disable_bundle_capability": {
      "limits": [
        {
          "counter": "disable_bundle_capability_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

Create a free account and register App Store Connect — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More App Store Connect tools

Destructive remove_tester_from_group Remove a tester from a beta group Write add_tester_to_group Add a new tester to a beta group Write create_analytics_report_request Create a new analytics report request for an app Write create_app_store_version Create a new app store version for an app Write create_bundle_id Register a new bundle ID for app development Write enable_bundle_capability Enable a capability for a bundle ID Write update_app_store_version_localization Update a specific field in an app store version localization Read download_analytics_report_segment Download data from an analytics report segment URL

All 27 App Store Connect tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about disable_bundle_capability

What does the disable_bundle_capability tool do? +

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

How do I enforce a policy on disable_bundle_capability? +

Register the App Store Connect MCP server in PolicyLayer and add a rule for disable_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.

What risk level is disable_bundle_capability? +

disable_bundle_capability is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit disable_bundle_capability? +

Yes. Add a rate_limit block to the disable_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.

How do I block disable_bundle_capability completely? +

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

What MCP server provides disable_bundle_capability? +

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

Enforce policy on every App Store Connect tool call.

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.

CHECK YOUR STACK →