asc_patch_age_rating_declaration
Answer the age-rating questionnaire. Every field is optional and Apple MERGES — omitted keys keep their current value, so a partial update is safe, but you cannot clear a field by omitting it (send the explicit NONE / false). Content questions take a frequency: NONE / INFREQUENT_OR_MILD / FREQUEN...
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-patch-age-rating-declaration.md
What asc_patch_age_rating_declaration does on Appstoreconnect Mcp
AI agents use asc_patch_age_rating_declaration 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_age_rating_declaration is rated Medium
Modifies age rating metadata affecting app store listing visibility and legal compliance, reversible via subsequent updates.
From the tool's definition PATCH age rating declaration; merges with current values; drives public age rating
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs asc_patch_age_rating_declaration safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appstoreconnect Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For asc_patch_age_rating_declaration, this is the rule to start with:
asc_patch_age_rating_declaration 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Appstoreconnect Mcp, apply this rule, and every asc_patch_age_rating_declaration call is checked against it from then on.
Questions about asc_patch_age_rating_declaration
Answer the age-rating questionnaire. Every field is optional and Apple MERGES — omitted keys keep their current value, so a partial update is safe, but you cannot clear a field by omitting it (send the explicit NONE / false). Content questions take a frequency: NONE / INFREQUENT_OR_MILD / FREQUENT_OR_INTENSE (some newer categories use INFREQUENT / FREQUENT). Raising any answer raises the computed rating. Overrides can only push the rating UP, never down. Writes to /v1/ageRatingDeclarations/{id}; the id equals the appInfo id and is resolved for you from appId. ⚠️ This drives the public age rating and can gate App Review — review the current answers with asc_get_age_rating_declaration first. 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.
Register the Appstoreconnect MCP server in PolicyLayer and add a rule for asc_patch_age_rating_declaration: 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.
asc_patch_age_rating_declaration 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 asc_patch_age_rating_declaration 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 asc_patch_age_rating_declaration. 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.
asc_patch_age_rating_declaration 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.
This server
Across the catalogue