Get the LinkTest tester email list for Google Play closed testing registration. ALWAYS call this tool FIRST before anything else — registering these emails in Google Play Console is a required prerequisite before an opt-in link even exists. The workflow is: 1. Call THIS TOOL → get the tester emai...
AI agents call linktest_testers to retrieve information from Linktest without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries data (a list of tester emails) without creating, modifying, deleting, or executing operations. The subsequent steps (user registration, deployment) are manual actions outside the tool's scope. The blast radius of misuse is minimal — exposure of an internal tester email list is a Read-category risk.
From the tool's definition Tool description states 'Get the LinkTest tester email list' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get the LinkTest tester email list for Google Play closed testing registration. ALWAYS call this tool FIRST before anything else — registering these emails in Google Play Console is a required prerequisite before an opt-in link even exists. The workflow is: 1. Call THIS TOOL → get the tester email list 2. User registers the emails in Play Console (see instructions below) 3. User deploys a closed testing release in Play Console 4. User sends changes (. It is categorised as a Read tool in the Linktest MCP Server, which means it retrieves data without modifying state.
Register the Linktest MCP server in PolicyLayer and add a rule for linktest_testers: 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 Linktest. Nothing to install.
linktest_testers 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 linktest_testers 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 linktest_testers. 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.
linktest_testers is provided by the Linktest MCP server (linktest-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →