appstore_upload_screenshot
A write tool on the Mimi Seed MCP server.
This record as markdown: /tools/yoonion-mimi-seed-mcp/appstore-upload-screenshot.md
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 appstore_upload_screenshot is rated Medium
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
The rule that runs appstore_upload_screenshot safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mimi Seed, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For appstore_upload_screenshot, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mimi Seed, apply this rule, and every appstore_upload_screenshot call is checked against it from then on.
Questions about appstore_upload_screenshot
appstore_upload_screenshot is a write tool on the Mimi Seed MCP server. 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.
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.
appstore_upload_screenshot 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 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.
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.
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.
More on Mimi Seed, and thousands of servers like it.
This server
Across the catalogue