asc_post_iap_price_schedule
Replace the price schedule for an in-app purchase (v2 IAPs only — consumables, non-consumables, non-renewing subs).
This record as markdown: /tools/io-github-akoskomuves-appstoreconnect-mcp/asc-post-iap-price-schedule.md
What asc_post_iap_price_schedule does on Appstoreconnect Mcp
AI agents use asc_post_iap_price_schedule 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_post_iap_price_schedule is rated Medium
This tool modifies pricing schedules for in-app purchases, which is a reversible write operation. Although pricing changes have financial implications, the tool itself does not move money or create financial obligations — it configures product pricing metadata.
From the tool's definition Tool name contains 'post' and description states 'Replace the price schedule' — these indicate modification of existing data (in-app purchase pricing).
Attacks that exploit this kind of access
The rule that runs asc_post_iap_price_schedule 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_post_iap_price_schedule, this is the rule to start with:
asc_post_iap_price_schedule 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_post_iap_price_schedule call is checked against it from then on.
Questions about asc_post_iap_price_schedule
Replace the price schedule for an in-app purchase (v2 IAPs only — consumables, non-consumables, non-renewing subs). 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_post_iap_price_schedule: 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_post_iap_price_schedule 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_post_iap_price_schedule 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_post_iap_price_schedule. 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_post_iap_price_schedule 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