appstore_create_inapp_purchase

WHAT IT DOES

What appstore_create_inapp_purchase does on Mimi Seed

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

WHY IT NEEDS A POLICY

Why appstore_create_inapp_purchase needs a policy

Creates or modifies data on App Store (in-app purchase product setup) rather than deleting it irreversibly, placing it in Write category. Severity is high because misconfiguration could expose unintended purchases, affect monetization, or create customer-facing issues.

From the tool's definition Tool name 'appstore_create_inapp_purchase' indicates creation of in-app purchase configuration on Apple App Store.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

appstore_create_inapp_purchase Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "appstore_create_inapp_purchase": {
      "limits": [
        {
          "counter": "appstore_create_inapp_purchase_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mimi Seed, so you can run agents against it safely.

FAQ

Questions about appstore_create_inapp_purchase

What does the appstore_create_inapp_purchase tool do? +

appstore_create_inapp_purchase. It is categorised as a Write tool in the Mimi Seed MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on appstore_create_inapp_purchase? +

Register the Mimi Seed MCP server in PolicyLayer and add a rule for appstore_create_inapp_purchase: 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 Mimi Seed. Nothing to install.

What risk level is appstore_create_inapp_purchase? +

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

Can I rate-limit appstore_create_inapp_purchase? +

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

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

appstore_create_inapp_purchase is provided by the Mimi Seed MCP server (@yoonion/mimi-seed-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

appstore_create_inapp_purchase is one line of Mimi Seed's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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