This record as markdown: /tools/io-github-kivanccakmak-yaver/playstore-status.md
What playstore_status does on Yaver
AI agents call playstore_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 |
|---|---|---|---|
package | string | Yes | Package name (e.g. io.yaver.mobile) |
Parameters from the server's own tool schema.
Why playstore_status is rated Low
This tool queries the Google Play Console to retrieve status information about an app. It performs no side effects, does not execute code or commands, does not modify data, and does not involve financial transactions. It is a straightforward read operation that retrieves information for inspection purposes.
From the tool's definition Tool name 'playstore_status' and description 'Check Google Play Console status for an app' indicate a query operation that retrieves status information without modifying or triggering actions.
Attacks that exploit this kind of access
The rule that runs playstore_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 playstore_status, this is the rule to start with:
playstore_status 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 playstore_status call is checked against it from then on.
Questions about playstore_status
Check Google Play Console status for an app. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
playstore_status accepts 1 parameter: package. Required: package. 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 playstore_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.
playstore_status 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 playstore_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.
Set action: deny in the PolicyLayer policy for playstore_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.
playstore_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.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue