appstore_list_screenshots

App Store 스크린샷 셋 + 이미지 목록 조회 (로컬라이제이션 단위). 디스플레이 타입별로 그룹핑됨

SERVERMimi Seed SOURCE@yoonion/mimi-seed-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yoonion-mimi-seed-mcp/appstore-list-screenshots.md

WHAT IT DOES

What appstore_list_screenshots does on Mimi Seed

AI agents call appstore_list_screenshots to retrieve information from Mimi Seed without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why appstore_list_screenshots is rated Low

This tool retrieves and displays existing screenshot metadata and image information organized by localization and display type. It performs no data creation, modification, deletion, or execution of external operations. It is a straightforward read operation with no side effects, making it a low-severity Read category tool.

From the tool's definition Tool name 'appstore_list_screenshots' and description indicate it performs a query/list operation to retrieve App Store screenshots and images. The verb 'list' and '조회' (query/retrieve in Korean) confirm data retrieval without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs appstore_list_screenshots 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 appstore_list_screenshots, this is the rule to start with:

appstore_list_screenshots Allowed

appstore_list_screenshots is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "appstore_list_screenshots": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mimi Seed, apply this rule, and every appstore_list_screenshots call is checked against it from then on.

FAQ

Questions about appstore_list_screenshots

What does the appstore_list_screenshots tool do? +

App Store 스크린샷 셋 + 이미지 목록 조회 (로컬라이제이션 단위). 디스플레이 타입별로 그룹핑됨. It is categorised as a Read tool in the Mimi Seed MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on appstore_list_screenshots? +

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

appstore_list_screenshots is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit appstore_list_screenshots? +

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

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

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

KEEP EXPLORING

More on Mimi Seed, and thousands of servers like it.

This server

All 230 Mimi Seed tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →