Verify and decode a payment transaction by its Solana signature. Confirms whether a specific payment was made.
AI agents call verify_payment_receipt to retrieve information from Agenti without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries transaction data on the Solana blockchain to verify and confirm payment receipt. It has no side effects—it does not move funds, execute code with variable outcomes, modify state, or delete data. While the broader agenti server enables financial operations, this specific tool is limited to reading transaction information.
From the tool's definition Tool performs verification and decoding of payment transactions ("Verify and decode a payment transaction") and confirmation of payment status ("Confirms whether a specific payment was made").
Documented attack patterns abuse exactly the kind of access verify_payment_receipt gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agenti, and nothing reaches the server without passing your rules. This is the rule we recommend for verify_payment_receipt:
{
"version": "1",
"default": "deny",
"tools": {
"verify_payment_receipt": {}
}
}verify_payment_receipt is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Verify and decode a payment transaction by its Solana signature. Confirms whether a specific payment was made. It is categorised as a Read tool in the Agenti MCP Server, which means it retrieves data without modifying state.
Register the Agenti MCP server in PolicyLayer and add a rule for verify_payment_receipt: 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 Agenti. Nothing to install.
verify_payment_receipt 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 verify_payment_receipt 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 verify_payment_receipt. 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.
verify_payment_receipt is provided by the Agenti MCP server (nirholas/agenti). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 73 Agenti tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
73 Agenti tools catalogued and risk-classified — across an index of 42,500+ MCP servers.