Create a payment request — returns an address and amount for someone to pay you
AI agents use create_invoice to commit financial operations through Agenti — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool creates financial instruments (invoices/payment requests) in a cryptocurrency context. The server is explicitly designed to 'hold, spend, earn, and receive cryptocurrency.' While creating an invoice is less severe than directly moving funds, it initiates a financial transaction flow and commits to receiving a specific cryptocurrency payment, which qualifies as a financial obligation/commitment.
From the tool's definition Create a payment request — returns an address and amount for someone to pay you
Documented attack patterns abuse exactly the kind of access create_invoice 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 create_invoice:
{
"version": "1",
"default": "deny",
"tools": {
"create_invoice": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}Any call to create_invoice is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Create a payment request — returns an address and amount for someone to pay you. It is categorised as a Financial tool in the Agenti MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Agenti MCP server in PolicyLayer and add a rule for create_invoice: 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.
create_invoice 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 create_invoice 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 create_invoice. 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.
create_invoice 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.