playstore_update_listing

Google Play 스토어 리스팅 수정 (제목, 설명문 변경). ⚠️ Play API 편집과 Console 동시 편집은 충돌 — Console에서 같은 리스팅을 편집·미게시 중이면 그 변경이 덮어써질 수 있음.

Server Mimi Seed @yoonion/mimi-seed-mcp
Category Write
Risk class Medium
Parameters 00 required

What playstore_update_listing does on Mimi Seed

AI agents use playstore_update_listing 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_update_listing needs a policy

The tool creates or modifies data (app store listing metadata) reversibly without deleting or executing code. While the warning about potential conflicts with concurrent Console edits increases the risk profile, the core action is Write.

From the tool's definition Tool name 'playstore_update_listing' and description states it modifies (수정) Play Store listing fields like title and description (제목, 설명문 변경). This is reversible modification of app metadata.

Questions about playstore_update_listing

What does the playstore_update_listing tool do? +

Google Play 스토어 리스팅 수정 (제목, 설명문 변경). ⚠️ Play API 편집과 Console 동시 편집은 충돌 — Console에서 같은 리스팅을 편집·미게시 중이면 그 변경이 덮어써질 수 있음. 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 playstore_update_listing? +

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

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

Can I rate-limit playstore_update_listing? +

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

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

playstore_update_listing 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

playstore_update_listing 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.