View payment history and get receipt details. Returns a list of all payments made, including amounts, dates, and order associations. Optionally provide a payment_id to get a specific receipt. Args: - payment_id (string, optional): Specific payment ID for receipt details. Omit for full history. Re...
AI agents call linktest_billing 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 only retrieves historical payment and receipt information. It has no capability to create charges, refund money, modify billing records, or execute financial transactions. The read-only nature and informational purpose place it squarely in the Read category with low severity, as misuse would only expose historical data rather than cause financial harm or irreversible changes.
From the tool's definition Tool description explicitly states 'View payment history and get receipt details' and 'Returns a list of all payments made'. The verb 'View' and 'get' indicate read-only retrieval operations.
Attacks that exploit this kind of access
View payment history and get receipt details. Returns a list of all payments made, including amounts, dates, and order associations. Optionally provide a payment_id to get a specific receipt. Args: - payment_id (string, optional): Specific payment ID for receipt details. Omit for full history. Returns (without payment_id): {. 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_billing: 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_billing 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_billing 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_billing. 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_billing 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 →