Report that an approved purchase has been completed externally. After getting approval via request_payment (or pay with payment_mode='external'), the agent pays using whatever payment method it has (AgentCard, privacy.com, etc), then calls this tool to confirm the purchase happened and close the ...
AI agents use report_purchase to commit financial operations through Tru — usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
notes | string | — | Any additional details about the purchase |
card_last4 | string | — | Last 4 digits of the card used |
request_id | string | Yes | The charge request ID from request_payment |
receipt_url | string | — | URL of the receipt if available |
payment_method | string | — | Description of how it was paid (e.g. 'AgentCard', 'privacy.com') |
Parameters from the server's own tool schema.
This tool records and confirms financial transactions involving real payment methods (AgentCard, privacy.com). It closes the audit loop on external purchases, meaning it finalizes financial obligations. Misuse could confirm fraudulent or unauthorized purchases, making it Financial category with critical severity.
From the tool's definition 'Report that an approved purchase has been completed externally', 'the agent pays using whatever payment method it has (AgentCard, privacy.com, etc)', 'confirm the purchase happened and close the audit loop'
Attacks that exploit this kind of access
Report that an approved purchase has been completed externally. After getting approval via request_payment (or pay with payment_mode='external'), the agent pays using whatever payment method it has (AgentCard, privacy.com, etc), then calls this tool to confirm the purchase happened and close the audit loop. Only works on charges with status 'approved' and no app_id (personal/external charges). It is categorised as a Financial tool in the Tru MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
report_purchase accepts 5 parameters: notes, card_last4, request_id, receipt_url, payment_method. Required: request_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 report_purchase: 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.
report_purchase is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the report_purchase 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 report_purchase. 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.
report_purchase 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 →