appstore_status

Check App Store Connect app status (review state, builds). Requires APP_STORE_API_KEY_ID and APP_STORE_API_ISSUER env vars.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/appstore-status.md

WHAT IT DOES

What appstore_status does on Yaver

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

Parameter	Type	Required	Description
`bundle_id`	string	—	Bundle ID (e.g. io.yaver.mobile)

Parameters from the server's own tool schema.

RISK

Why appstore_status is rated Low

The tool performs read-only operations against App Store Connect API, retrieving metadata about app review states and build information. It requires API credentials but does not create, modify, delete, or execute code/commands. The blast radius of misuse is limited to information disclosure about app deployment status.

From the tool's definition Tool name is 'appstore_status' and description states it 'Check[s] App Store Connect app status (review state, builds)' — these are query operations that retrieve information about application state without modifying or executing anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs appstore_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For appstore_status, this is the rule to start with:

appstore_status Allowed

appstore_status 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_status": {}
  }
}

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

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

FAQ

Questions about appstore_status

What does the appstore_status tool do? +

Check App Store Connect app status (review state, builds). Requires APP_STORE_API_KEY_ID and APP_STORE_API_ISSUER env vars. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does appstore_status accept? +

appstore_status accepts 1 parameter: bundle_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on appstore_status? +

Register the Yaver MCP server in PolicyLayer and add a rule for appstore_status: 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 Yaver. Nothing to install.

What risk level is appstore_status? +

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

Can I rate-limit appstore_status? +

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

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

appstore_status is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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