AI agents use create_bundle_id 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 a new bundle ID, which is a reversible write operation that adds a configuration resource to Apple's development infrastructure. While it modifies the developer's account state, the operation can be undone by unregistering the bundle ID. It does not execute arbitrary code, delete data, or involve financial transactions.
From the tool's definition Tool name 'create_bundle_id' and description 'Register a new bundle ID for app development' indicate creation of a new resource in the App Store Connect system.
Documented attack patterns abuse exactly the kind of access create_bundle_id 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 create_bundle_id:
{
"version": "1",
"default": "deny",
"tools": {
"create_bundle_id": {
"limits": [
{
"counter": "create_bundle_id_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_bundle_id 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.
Register a new bundle ID for app development. 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 create_bundle_id: 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.
create_bundle_id 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 create_bundle_id 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 create_bundle_id. 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.
create_bundle_id 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.