app_review_check
Get App Store / Play Store review guidelines, common rejection reasons, and pre-submission checklist.
This record as markdown: /tools/io-github-kivanccakmak-yaver/app-review-check.md
What app_review_check does on Yaver
AI agents call app_review_check 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 |
|---|---|---|---|
platform | string | — | ios or android (both if empty) |
Parameters from the server's own tool schema.
Why app_review_check is rated Low
This tool reads and returns static reference information (guidelines, rejection reasons, checklists) to inform development decisions. It has no side effects, does not execute code, does not modify data, and does not commit any irreversible or financial actions. The primary purpose is to query and retrieve pre-existing policy and guidance data.
From the tool's definition Tool description states 'Get App Store / Play Store review guidelines, common rejection reasons, and pre-submission checklist' — these are retrieval operations that return informational data without modifying any system state or triggering external operations.
Attacks that exploit this kind of access
The rule that runs app_review_check 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 app_review_check, this is the rule to start with:
app_review_check is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every app_review_check call is checked against it from then on.
Questions about app_review_check
Get App Store / Play Store review guidelines, common rejection reasons, and pre-submission checklist. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
app_review_check accepts 1 parameter: platform. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for app_review_check: 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.
app_review_check is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the app_review_check 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 app_review_check. 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.
app_review_check 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.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue