googleplay_data_safety
Fetch a Google Play app's declared data-safety disclosure Fetch a Google Play app's declared data-safety disclosure. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/googleplay/data_safety/{id}
This record as markdown: /tools/com-replynodes-mcp/googleplay-data-safety.md
What googleplay_data_safety does on ReplyNodes
AI agents call googleplay_data_safety to retrieve information from ReplyNodes 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 |
|---|---|---|---|
id | string | Yes | Google Play package id (e.g. com.nike.snkrs). |
country | string | — | Two-letter storefront code. |
language | string | — | Language code. |
Parameters from the server's own tool schema.
Why googleplay_data_safety is rated Low
Retrieves publicly declared app safety data from Google Play without modification or external effects.
From the tool's definition Fetch declared data-safety disclosure; public contract; no side effects.
Attacks that exploit this kind of access
The rule that runs googleplay_data_safety safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ReplyNodes, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For googleplay_data_safety, this is the rule to start with:
googleplay_data_safety 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 ReplyNodes, apply this rule, and every googleplay_data_safety call is checked against it from then on.
Questions about googleplay_data_safety
Fetch a Google Play app's declared data-safety disclosure Fetch a Google Play app's declared data-safety disclosure. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/googleplay/data_safety/{id}. It is categorised as a Read tool in the ReplyNodes MCP Server, which means it retrieves data without modifying state.
googleplay_data_safety accepts 3 parameters: id, country, language. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the ReplyNodes MCP server in PolicyLayer and add a rule for googleplay_data_safety: 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 ReplyNodes. Nothing to install.
googleplay_data_safety 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 googleplay_data_safety 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 googleplay_data_safety. 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.
googleplay_data_safety is provided by the ReplyNodes MCP server (https://mcp.replynodes.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ReplyNodes, and thousands of servers like it.
This server
Across the catalogue