AI agents call check_payment_status to retrieve information from Tru without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
charge_id | string | Yes | The charge request ID to check |
Parameters from the server's own tool schema.
This tool only retrieves and reports the current state of a payment or subscription without modifying, creating, or destroying anything. It is informational in nature. Although it operates in a financial domain, the tool itself performs no financial action (no money moves, no obligations created). The blast radius is minimal: an AI agent cannot harm the system or user by checking payment status.
From the tool's definition Tool description states it 'Check[s] the status' and 'Returns pending, approved, rejected, or cancelled' — a pure query operation with no side effects.
Attacks that exploit this kind of access
Check the status of a charge or subscription request. Returns pending, approved, rejected, or cancelled. It is categorised as a Read tool in the Tru MCP Server, which means it retrieves data without modifying state.
check_payment_status accepts 1 parameter: charge_id. Required: charge_id. The full parameter table on this page comes from the server's own tool schema.
Register the Tru MCP server in PolicyLayer and add a rule for check_payment_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 Tru. Nothing to install.
check_payment_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 check_payment_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 check_payment_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.
check_payment_status is provided by the Tru MCP server (tru-mcp). 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 →