appstore_upload_screenshot · Mimi Seed MCP: Risk & Policy

WHAT IT DOES

What appstore_upload_screenshot does on Mimi Seed

AI agents use appstore_upload_screenshot 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_upload_screenshot needs a policy

The tool performs an upload action to the App Store, which creates or modifies assets (screenshots) reversibly. This is a Write operation rather than Read (no query/fetch), Execute (not triggering external code execution with variable effects), or Destructive (screenshots can be replaced/removed). Severity is medium because misuse could alter app store presence and user experience, but the action is reversible.

From the tool's definition Tool name 'appstore_upload_screenshot' indicates uploading/modifying app store assets. The description is empty, but the sibling tools show this server manages App Store operations (appstore_attach_build visible), and upload operations typically create or…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

appstore_upload_screenshot Rate-limited

appstore_upload_screenshot 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_upload_screenshot": {
      "limits": [
        {
          "counter": "appstore_upload_screenshot_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_upload_screenshot

What does the appstore_upload_screenshot tool do? +

appstore_upload_screenshot. 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_upload_screenshot? +

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

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

Can I rate-limit appstore_upload_screenshot? +

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

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

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