ebay_upload_payment_dispute_evidence_file
Upload a file as evidence for a payment dispute (e.g., shipping receipt, photos). Returns a file ID to use with add_evidence.\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-upload-payment-dispute-evidence-file.md
What ebay_upload_payment_dispute_evidence_file does on Ebay
AI agents use ebay_upload_payment_dispute_evidence_file to create or update resources in Ebay, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ebay environment.
Why ebay_upload_payment_dispute_evidence_file is rated Medium
This tool writes/creates data (evidence files) in eBay's dispute management system. While file upload is generally reversible (files can be deleted), it modifies dispute records and could be misused to add fraudulent evidence to disputes, affecting financial liability determinations.
From the tool's definition Tool uploads a file as evidence for a payment dispute, creating new evidence record(s) in the dispute system. Description states 'Upload a file' and 'Returns a file ID to use with add_evidence', indicating file creation and persistence.
Attacks that exploit this kind of access
The rule that runs ebay_upload_payment_dispute_evidence_file 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_upload_payment_dispute_evidence_file, this is the rule to start with:
ebay_upload_payment_dispute_evidence_file stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_upload_payment_dispute_evidence_file call is checked against it from then on.
Questions about ebay_upload_payment_dispute_evidence_file
Upload a file as evidence for a payment dispute (e.g., shipping receipt, photos). Returns a file ID to use with add_evidence.\n\nRequired OAuth Scope: sell.fulfillment\nMinimum Scope: https://api.ebay.com/oauth/api_scope/sell.fulfillment. It is categorised as a Write tool in the Ebay MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ebay MCP server in PolicyLayer and add a rule for ebay_upload_payment_dispute_evidence_file: 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_upload_payment_dispute_evidence_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ebay_upload_payment_dispute_evidence_file 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_upload_payment_dispute_evidence_file. 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_upload_payment_dispute_evidence_file 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