AI agents use playstore_reply_review 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.
This tool posts a reply to a user review on Google Play Store. It creates/modifies publicly visible content (the developer reply), which is a reversible write operation. It does not delete anything, execute arbitrary code, or involve financial transactions. Misuse could post inappropriate responses to user reviews, damaging brand reputation, hence medium severity.
From the tool's definition playstore_reply_review — 'Google Play 리뷰에 답변' (Reply to Google Play review)
Attacks that exploit this kind of access
Google Play 리뷰에 답변. 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_reply_review: 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_reply_review 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_reply_review 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_reply_review. 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_reply_review 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.
playstore_reply_review 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 →