AI agents invoke playstore_promote_release to trigger actions in Mimi Seed. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Based on the name, this tool likely promotes a release on the Google Play Store (e.g., advancing a release from internal/alpha/beta to production), which is an external operation with significant real-world impact. However, the description is empty, so confidence is lowered.
From the tool's definition Tool name 'playstore_promote_release' and server context involving Google Play management; description is empty and uninformative.
Attacks that exploit this kind of access
playstore_promote_release. It is categorised as a Execute tool in the Mimi Seed MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mimi Seed MCP server in PolicyLayer and add a rule for playstore_promote_release: 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_promote_release is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the playstore_promote_release 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_promote_release. 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_promote_release 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_promote_release 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 →