playstore_track
Check Play Store track status (production, beta, alpha).
This record as markdown: /tools/io-github-kivanccakmak-yaver/playstore-track.md
What playstore_track does on Yaver
AI agents call playstore_track 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 |
|---|---|---|---|
track | string | — | Track: production, beta, alpha, internal (default: production) |
package | string | Yes |
Parameters from the server's own tool schema.
Why playstore_track is rated Low
This tool retrieves the current status of an app's distribution track on the Google Play Store (production, beta, or alpha). It performs a passive query with no ability to modify, delete, or execute code. The blast radius of misuse is minimal—an attacker could only learn which track an app is in, without affecting any systems or data.
From the tool's definition Tool name 'playstore_track' with description 'Check Play Store track status' indicates a query/retrieval operation. The verb 'check' and the read-only nature of status checks confirm this is information retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs playstore_track 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_track, this is the rule to start with:
playstore_track 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_track call is checked against it from then on.
Questions about playstore_track
Check Play Store track status (production, beta, alpha). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
playstore_track accepts 2 parameters: track, 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_track: 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_track 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_track 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_track. 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_track 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