check_payment
Check whether a payment invoice has been fulfilled by querying the chain
This record as markdown: /tools/nirholas-agenti/check-payment.md
What check_payment does on Agenti
AI agents call check_payment to retrieve information from Agenti without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_payment is rated Low
The tool performs a passive lookup/query of blockchain state to verify payment status. Despite the financial context (payment domain), the tool itself does not move money, execute transactions, or modify data. It is purely informational retrieval. Severity is low because misuse would only return incorrect information, not cause financial harm or irreversible damage.
From the tool's definition Tool description states "Check whether a payment invoice has been fulfilled by querying the chain" — a read-only query operation with no modifications or state changes.
Attacks that exploit this kind of access
The rule that runs check_payment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agenti, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_payment, this is the rule to start with:
check_payment is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Agenti, apply this rule, and every check_payment call is checked against it from then on.
Questions about check_payment
Check whether a payment invoice has been fulfilled by querying the chain. 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 check_payment: 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.
check_payment 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 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. 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 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.
More on Agenti, and thousands of servers like it.
This server
Across the catalogue