Create a payment invoice so another party can send funds to this agent.
AI agents use agenti_receive to commit financial operations through Agenti — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool initiates a financial transaction by creating a payment invoice for receiving cryptocurrency funds. While receiving funds is less risky than sending, it still constitutes a financial operation that could be misused (e.g., soliciting payments from unintended parties, creating fraudulent invoices). Financial category takes precedence over all others per the severity hierarchy.
From the tool's definition "Create a payment invoice so another party can send funds to this agent" — directly involves cryptocurrency financial transactions; server description explicitly states 'hold, spend, earn, and receive cryptocurrency'
Documented attack patterns abuse exactly the kind of access agenti_receive 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 agenti_receive:
{
"version": "1",
"default": "deny",
"tools": {
"agenti_receive": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to agenti_receive is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Create a payment invoice so another party can send funds to this agent. 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 agenti_receive: 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.
agenti_receive 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 agenti_receive 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 agenti_receive. 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.
agenti_receive 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.