appstore_verify_credentials

App Store Connect API 키(appstore.json) 유효성 검증 — JWT 서명 + GET /apps 호출로 creds/sign/auth/api 단계별 진단. 첫 도구 호출에서 401로 늦게 터지기 전에 setup 직후 확인용. 인자 없음.

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

What appstore_verify_credentials does on Mimi Seed

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

Why appstore_verify_credentials needs a policy

This tool queries and validates App Store Connect API credentials through a read-only GET request. It performs authentication testing and diagnostics without creating, modifying, deleting, or executing any operations. The purpose is to verify credentials before other tools are called, making it a pure read/diagnostic operation with minimal blast radius.

From the tool's definition Tool performs validation by making 'GET /apps' API call and checking JWT signature/authentication status. Description indicates it's diagnostic (진단) with 'no arguments' (인자 없음), checking credentials without modifying or executing operations.

Questions about appstore_verify_credentials

What does the appstore_verify_credentials tool do? +

App Store Connect API 키(appstore.json) 유효성 검증 — JWT 서명 + GET /apps 호출로 creds/sign/auth/api 단계별 진단. 첫 도구 호출에서 401로 늦게 터지기 전에 setup 직후 확인용. 인자 없음. 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_verify_credentials? +

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

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

Can I rate-limit appstore_verify_credentials? +

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

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

appstore_verify_credentials 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

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