New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

asc_delete_bundle_id_capability

Disable a capability (DELETE the capability record). Apps relying on the entitlement lose it on their next profile regeneration — verify nothing ships with it first.

SERVERAppstoreconnect Mcp SOURCE@akoskomuves/appstoreconnect-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-delete-bundle-id-capability.md

What asc_delete_bundle_id_capability does on Appstoreconnect Mcp

AI agents call asc_delete_bundle_id_capability to permanently remove resources in Appstoreconnect Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why asc_delete_bundle_id_capability is rated Critical

Irreversibly removes entitlements from app capabilities affecting production applications.

From the tool's definition DELETE capability record, apps lose entitlement, cannot be undone

Questions about asc_delete_bundle_id_capability

What does the asc_delete_bundle_id_capability tool do? +

Disable a capability (DELETE the capability record). Apps relying on the entitlement lose it on their next profile regeneration — verify nothing ships with it first. It is categorised as a Destructive tool in the Appstoreconnect Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on asc_delete_bundle_id_capability? +

Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_delete_bundle_id_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 Appstoreconnect Mcp. Nothing to install.

What risk level is asc_delete_bundle_id_capability? +

asc_delete_bundle_id_capability is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit asc_delete_bundle_id_capability? +

Yes. Add a rate_limit block to the asc_delete_bundle_id_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 asc_delete_bundle_id_capability completely? +

Set action: deny in the PolicyLayer policy for asc_delete_bundle_id_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 asc_delete_bundle_id_capability? +

asc_delete_bundle_id_capability is provided by the Appstoreconnect MCP server (@akoskomuves/appstoreconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Appstoreconnect, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Appstoreconnect's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.