AI agents call get_dispute to retrieve information from PayPal without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and queries dispute information without modifying, deleting, or triggering any financial transactions. While it operates in a financial domain (PayPal disputes), the action itself is purely informational—fetching details about an existing dispute. No money moves, no data is altered, and no irreversible actions occur. This is a classic Read operation.
From the tool's definition Tool name 'get_dispute' and description 'Retrieve detailed information of a specific dispute' indicate a data retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_dispute gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PayPal, and nothing reaches the server without passing your rules. This is the rule we recommend for get_dispute:
{
"version": "1",
"default": "deny",
"tools": {
"get_dispute": {}
}
}get_dispute is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve detailed information of a specific dispute. It is categorised as a Read tool in the PayPal MCP Server, which means it retrieves data without modifying state.
Register the PayPal MCP server in PolicyLayer and add a rule for get_dispute: 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.
get_dispute is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_dispute 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 get_dispute. 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.
get_dispute is provided by the PayPal MCP server (paypal/agent-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 30 PayPal tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
30 PayPal tools catalogued and risk-classified — across an index of 42,500+ MCP servers.