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

asc_patch_nomination

⚠️ PATCH a nomination. Apple REQUIRES submitted or archived on EVERY patch (400 PARAMETER_ERROR.REQUIRED otherwise — caught live 2026-08-13): pass submitted:false when editing a draft (keeps it a draft), submitted:true to SEND it to Apple

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

This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-patch-nomination.md

What asc_patch_nomination does on Appstoreconnect Mcp

AI agents use asc_patch_nomination to create or update resources in Appstoreconnect Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Appstoreconnect Mcp environment.

Why asc_patch_nomination is rated Medium

Modifies nomination state with submission capability; affects app review process but reversible.

From the tool's definition PATCH a nomination. submitted parameter controls draft vs. send to Apple.

Risk signalsBulk/mass operation — affects multiple targets

Questions about asc_patch_nomination

What does the asc_patch_nomination tool do? +

⚠️ PATCH a nomination. Apple REQUIRES submitted or archived on EVERY patch (400 PARAMETER_ERROR.REQUIRED otherwise — caught live 2026-08-13): pass submitted:false when editing a draft (keeps it a draft), submitted:true to SEND it to Apple. It is categorised as a Write tool in the Appstoreconnect Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on asc_patch_nomination? +

Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_patch_nomination: 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_patch_nomination? +

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

Can I rate-limit asc_patch_nomination? +

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

Set action: deny in the PolicyLayer policy for asc_patch_nomination. 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_patch_nomination? +

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