playstore_upload_image
Google Play 리스팅 이미지 단일 업로드 (기존 이미지 유지). featureGraphic 1024x500 / icon 512x512 / phoneScreenshots 320~3840px. ⚠️ 이 작업은 edit을 commit하므로 Play Console의 미게시(저장 전) 리스팅 변경을 덮어쓸 수 있음 — Console에서 같은 앱을 편집 중이면 먼저 저장·게시하거나 텍스트도 update_listing으로 처리하세요.
This record as markdown: /tools/yoonion-mimi-seed-mcp/playstore-upload-image.md
What playstore_upload_image does on Mimi Seed
AI agents use playstore_upload_image 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 playstore_upload_image is rated Medium
This tool creates or modifies app store listing data (images and metadata) in a reversible manner — images can be replaced or removed later. It does not delete data (Destructive), execute arbitrary code (Execute), or involve payments (Financial). While it affects production app store visibility, the changes are reversible through the Google Play Console, making it Write rather than Destructive.
From the tool's definition Tool uploads and modifies Google Play listing images (featureGraphic, icon, phoneScreenshots). Description explicitly states '이 작업은 edit을 commit하므로' (this operation commits the edit), indicating persistent changes to app store metadata.
Attacks that exploit this kind of access
The rule that runs playstore_upload_image 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 playstore_upload_image, this is the rule to start with:
playstore_upload_image 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 playstore_upload_image call is checked against it from then on.
Questions about playstore_upload_image
Google Play 리스팅 이미지 단일 업로드 (기존 이미지 유지). featureGraphic 1024x500 / icon 512x512 / phoneScreenshots 320~3840px. ⚠️ 이 작업은 edit을 commit하므로 Play Console의 미게시(저장 전) 리스팅 변경을 덮어쓸 수 있음 — Console에서 같은 앱을 편집 중이면 먼저 저장·게시하거나 텍스트도 update_listing으로 처리하세요. 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 playstore_upload_image: 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.
playstore_upload_image 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 playstore_upload_image 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 playstore_upload_image. 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.
playstore_upload_image 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