agenti_receive

Create a payment invoice so another party can send funds to this agent.

SERVERAgenti SOURCEnirholas/agenti

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nirholas-agenti/agenti-receive.md

WHAT IT DOES

What agenti_receive does on Agenti

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.

RISK

Why agenti_receive is rated Critical

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'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs agenti_receive 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 agenti_receive, this is the rule to start with:

agenti_receive Approval-gated

Any call to agenti_receive is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "agenti_receive": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Agenti, apply this rule, and every agenti_receive call is checked against it from then on.

FAQ

Questions about agenti_receive

What does the agenti_receive tool do? +

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.

How do I enforce a policy on agenti_receive? +

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.

What risk level is agenti_receive? +

agenti_receive is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit agenti_receive? +

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.

How do I block agenti_receive completely? +

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.

What MCP server provides agenti_receive? +

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.

KEEP EXPLORING

More on Agenti, and thousands of servers like it.

This server

All 73 Agenti tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →