This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/paypal-invoices.md
What paypal_invoices does on UnClick
AI agents use paypal_invoices to commit financial operations through UnClick, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | number | — | |
action | string | — | list, create, or send (default: list) |
invoice | object | — | Invoice object for action='create' |
sandbox | boolean | — | |
client_id | string | Yes | |
page_size | number | — | |
invoice_id | string | — | Required for action='send' |
client_secret | string | Yes |
Parameters from the server's own tool schema.
Why paypal_invoices is rated Critical
This tool can create and send PayPal invoices, which constitutes committing financial obligations and initiating payment requests. Creating and sending invoices directly involves financial transactions. The Financial category applies as the most severe, and the blast radius is critical since a misused agent could send fraudulent or erroneous invoices to customers.
From the tool's definition List, create, or send PayPal invoices
Attacks that exploit this kind of access
The rule that runs paypal_invoices safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For paypal_invoices, this is the rule to start with:
Any call to paypal_invoices is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every paypal_invoices call is checked against it from then on.
Questions about paypal_invoices
List, create, or send PayPal invoices. It is categorised as a Financial tool in the UnClick MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
paypal_invoices accepts 8 parameters: page, action, invoice, sandbox, client_id, page_size, invoice_id, client_secret. Required: client_id, client_secret. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for paypal_invoices: 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 UnClick. Nothing to install.
paypal_invoices 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 paypal_invoices 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 paypal_invoices. 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.
paypal_invoices is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
Across the catalogue