Low Risk

paypal_get_order

Get full details of a PayPal order by ID (e.g., "3JU84394D694620H"). Returns buyer info, items, amounts, and fulfillment status.

Part of the Paypal server.

paypal_get_order is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE PAYPAL →

Free to start. No card required.

AI agents call paypal_get_order to retrieve information from Paypal without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though paypal_get_order only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "paypal_get_order": {}
  }
}

See the full Paypal policy for all 25 tools.

Get this rule live on your own Paypal server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY PAYPAL →

View all 25 tools →

These attack patterns abuse exactly the kind of access paypal_get_order gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so paypal_get_order only ever does what you allow.

SECURE PAYPAL →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the paypal_get_order tool do? +

Get full details of a PayPal order by ID (e.g., "3JU84394D694620H"). Returns buyer info, items, amounts, and fulfillment status.. It is categorised as a Read tool in the Paypal MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on paypal_get_order? +

Register the Paypal MCP server in PolicyLayer and add a rule for paypal_get_order: 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.

What risk level is paypal_get_order? +

paypal_get_order is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit paypal_get_order? +

Yes. Add a rate_limit block to the paypal_get_order 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 paypal_get_order completely? +

Set action: deny in the PolicyLayer policy for paypal_get_order. 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 paypal_get_order? +

paypal_get_order is provided by the Paypal MCP server (https://gateway.pipeworx.io/paypal/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Paypal tool call.

Deterministic rules across all 25 Paypal tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.