New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

appstore_delete_screenshot_set

App Store 스크린샷 셋 전체 삭제 (디스플레이 타입 교체 시 먼저 정리)

SERVERMimi Seed SOURCE@yoonion/mimi-seed-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yoonion-mimi-seed-mcp/appstore-delete-screenshot-set.md

What appstore_delete_screenshot_set does on Mimi Seed

AI agents call appstore_delete_screenshot_set to permanently remove resources in Mimi Seed, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why appstore_delete_screenshot_set is rated Critical

This tool permanently deletes App Store screenshot sets without recovery option. While not as critical as production data deletion, losing all screenshots breaks app store listings and requires manual re-upload. The irreversible nature and potential for user error (e.g., deleting wrong app's assets) warrants Destructive classification at high severity.

From the tool's definition Tool name contains 'delete' and description translates to 'Delete entire App Store screenshot set' — irreversible removal of app store assets.

Questions about appstore_delete_screenshot_set

What does the appstore_delete_screenshot_set tool do? +

App Store 스크린샷 셋 전체 삭제 (디스플레이 타입 교체 시 먼저 정리). It is categorised as a Destructive tool in the Mimi Seed MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on appstore_delete_screenshot_set? +

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

appstore_delete_screenshot_set is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit appstore_delete_screenshot_set? +

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

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

appstore_delete_screenshot_set 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mimi Seed's. Pull the full record:

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.