Check the status of one or all LinkTest orders. If order_id is provided, returns detailed info about that specific order. If omitted, returns a summary list of all orders. Args: - order_id (string, optional): Specific order ID to look up. If omitted, lists all orders. Returns (with order_id): Det...
AI agents call linktest_status 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 performs a pure data retrieval operation—it queries order status information without side effects. It matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' Severity is low because exposure of historical order status information poses minimal risk to the system, though an agent with access could gather business intelligence about testing operations.
From the tool's definition Tool description states it 'Check[s] the status of one or all LinkTest orders' and returns 'Detailed order info' or 'List of all orders.' No modification, deletion, execution, or financial operations are performed. The tool only queries and retrieves data.
Attacks that exploit this kind of access
Check the status of one or all LinkTest orders. If order_id is provided, returns detailed info about that specific order. If omitted, returns a summary list of all orders. Args: - order_id (string, optional): Specific order ID to look up. If omitted, lists all orders. Returns (with order_id): Detailed order info including: - Package name, status, days remaining - Number of devices installed (out of 20) - Start date, expiry date - Opt-in link Returns (without order_id): List of all orders with: - Order ID, package name, status, days left, device count Status values: - pending: Awaiting payment - active: Testing in progress on devices - completed: Test period finished - expired: Expired without completing - payment_failed: Payment was not completed - failed: Tester emails not registered — devices could not install the app Examples: - Use when:. 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_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 Linktest. Nothing to install.
linktest_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 linktest_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 linktest_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.
linktest_status 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 →