This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/paypal-orders.md
What paypal_orders does on UnClick
AI agents use paypal_orders 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 |
|---|---|---|---|
action | string | — | create or get (default: get) |
intent | string | — | CAPTURE or AUTHORIZE (default: CAPTURE) |
sandbox | boolean | — | Use PayPal sandbox (default: false) |
order_id | string | — | Required for action='get' |
client_id | string | Yes | PayPal application Client ID |
client_secret | string | Yes | PayPal application Client Secret |
purchase_units | array | — | Required for action='create' |
Parameters from the server's own tool schema.
Why paypal_orders is rated Critical
The tool can create PayPal orders, which directly commits financial obligations or initiates payment transactions. 'Create' implies initiating a real financial transaction on PayPal's platform. Even though retrieval is also mentioned, the creation aspect makes this Financial and critical severity due to potential monetary impact if misused.
From the tool's definition Create or retrieve a PayPal order
Attacks that exploit this kind of access
The rule that runs paypal_orders 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_orders, this is the rule to start with:
Any call to paypal_orders 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_orders call is checked against it from then on.
Questions about paypal_orders
Create or retrieve a PayPal order. 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_orders accepts 7 parameters: action, intent, sandbox, order_id, client_id, client_secret, purchase_units. 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_orders: 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_orders 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_orders 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_orders. 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_orders 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