This record as markdown: /tools/paypal/send-invoice.md
What send_invoice does on PayPal
AI agents use send_invoice to commit financial operations through PayPal, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why send_invoice is rated Critical
This tool sends invoices which are financial documents that create payment obligations and commit monetary transactions. While not directly moving money like a payment would, invoicing is a critical step in financial workflows that can obligate parties to pay. The high severity reflects that a compromised AI agent could send fraudulent invoices to arbitrary recipients, causing financial and reputational harm.
From the tool's definition Tool is part of PayPal server with sibling tools including create_invoice, create_refund, create_subscription, and create_order. The tool name 'send_invoice' combined with PayPal context indicates financial operations.
Attacks that exploit this kind of access
The rule that runs send_invoice safely
PolicyLayer is an MCP gateway: it sits between your AI agents and PayPal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For send_invoice, this is the rule to start with:
Any call to send_invoice is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect PayPal, apply this rule, and every send_invoice call is checked against it from then on.
Questions about send_invoice
Send an invoice to recipients. It is categorised as a Financial tool in the PayPal MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the PayPal MCP server in PolicyLayer and add a rule for send_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 PayPal. Nothing to install.
send_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 send_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 send_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.
send_invoice is provided by the PayPal MCP server (@modelcontextprotocol/server-paypal). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on PayPal, and thousands of servers like it.
Across the catalogue