ebay_get_payment_dispute_activities
Get activity history for a payment dispute, including all actions taken by buyer, seller, and eBay.\n\nRequired OAuth Scope: sell.fulfillment\nMinimum Scope: https://api.ebay.com/oauth/api_scope/sell.fulfillment
This record as markdown: /tools/yosefhayim-ebay-mcp/ebay-get-payment-dispute-activities.md
What ebay_get_payment_dispute_activities does on Ebay
AI agents call ebay_get_payment_dispute_activities to retrieve information from Ebay without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why ebay_get_payment_dispute_activities is rated Low
This tool retrieves historical information about payment dispute activities. It has no side effects, makes no modifications, and does not execute code or trigger external operations. The scope requirement (sell.fulfillment) indicates it accesses seller fulfillment data for informational purposes. This is a straightforward Read category tool with low severity since it only exposes query access to dispute history.
From the tool's definition Tool name contains 'get' and description states 'Get activity history' - retrieves and queries payment dispute activity data without modifying or deleting anything.
Attacks that exploit this kind of access
The rule that runs ebay_get_payment_dispute_activities safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ebay, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ebay_get_payment_dispute_activities, this is the rule to start with:
ebay_get_payment_dispute_activities is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ebay, apply this rule, and every ebay_get_payment_dispute_activities call is checked against it from then on.
Questions about ebay_get_payment_dispute_activities
Get activity history for a payment dispute, including all actions taken by buyer, seller, and eBay.\n\nRequired OAuth Scope: sell.fulfillment\nMinimum Scope: https://api.ebay.com/oauth/api_scope/sell.fulfillment. It is categorised as a Read tool in the Ebay MCP Server, which means it retrieves data without modifying state.
Register the Ebay MCP server in PolicyLayer and add a rule for ebay_get_payment_dispute_activities: 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 Ebay. Nothing to install.
ebay_get_payment_dispute_activities 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 ebay_get_payment_dispute_activities 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 ebay_get_payment_dispute_activities. 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.
ebay_get_payment_dispute_activities is provided by the Ebay MCP server (yosefhayim/ebay-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ebay, and thousands of servers like it.
This server
Across the catalogue