linktest_retry · Linktest MCP: Risk & Policy

WHAT IT DOES

What linktest_retry does on Linktest

AI agents use linktest_retry to create or update resources in Linktest — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linktest environment.

WHY IT NEEDS A POLICY

Why linktest_retry needs a policy

This tool modifies the state of an existing order by requesting a retry, extending the testing period. It creates a new testing cycle and changes order status, which is a reversible write operation. It does not delete data, execute arbitrary code, or move money directly, though it may have indirect service implications. Confidence is slightly reduced because the description is truncated ('Order must be...').

From the tool's definition Request a free retry for a closed testing order that was rejected by Google Play... extends testing by another 14 days

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

linktest_retry Rate-limited

linktest_retry stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "linktest_retry": {
      "limits": [
        {
          "counter": "linktest_retry_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Linktest, so you can run agents against it safely.

FAQ

Questions about linktest_retry

What does the linktest_retry tool do? +

Request a free retry for a closed testing order that was rejected by Google Play. After 14+ days of testing, if Google Play rejects the production readiness review, the user can request ONE free retry per order. This extends testing by another 14 days. Conditions: - Order must be. It is categorised as a Write tool in the Linktest MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on linktest_retry? +

Register the Linktest MCP server in PolicyLayer and add a rule for linktest_retry: 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.

What risk level is linktest_retry? +

linktest_retry is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit linktest_retry? +

Yes. Add a rate_limit block to the linktest_retry 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.

How do I block linktest_retry completely? +

Set action: deny in the PolicyLayer policy for linktest_retry. 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.

What MCP server provides linktest_retry? +

linktest_retry 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.