appstore_create_version · Mimi Seed MCP: Risk & Policy

WHAT IT DOES

What appstore_create_version does on Mimi Seed

AI agents use appstore_create_version 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_version needs a policy

Creating an app version on App Store is a Write operation—it creates new app metadata/build records that can be modified or rolled back. Not Destructive (reversible), not Execute (no arbitrary code), not Financial (no direct payment movement, though release could have revenue impact). Severity is high because a malicious actor could publish unauthorized app versions affecting user distribution and trust.

From the tool's definition Tool name 'appstore_create_version' suggests creation of a new version in Apple App Store. Server context shows it manages App Store operations. Empty description limits certainty, but 'create' verb and App Store versioning imply app release staging.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

appstore_create_version Rate-limited

appstore_create_version 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_version": {
      "limits": [
        {
          "counter": "appstore_create_version_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_version

What does the appstore_create_version tool do? +

appstore_create_version. 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_version? +

Register the Mimi Seed MCP server in PolicyLayer and add a rule for appstore_create_version: 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_version? +

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

Can I rate-limit appstore_create_version? +

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

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

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