ebay_fetch_payment_dispute_evidence_content
Download evidence file content from a payment dispute.\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-fetch-payment-dispute-evidence-content.md
What ebay_fetch_payment_dispute_evidence_content does on Ebay
AI agents call ebay_fetch_payment_dispute_evidence_content 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_fetch_payment_dispute_evidence_content is rated Low
This tool retrieves/downloads existing evidence content from a payment dispute. It performs a read-only operation that queries and returns data without creating, modifying, deleting, or executing any actions. The scope is limited to seller fulfillment information. No irreversible changes, financial movements, or code execution are involved.
From the tool's definition Tool name contains 'fetch' and description states 'Download evidence file content from a payment dispute' - both indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs ebay_fetch_payment_dispute_evidence_content 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_fetch_payment_dispute_evidence_content, this is the rule to start with:
ebay_fetch_payment_dispute_evidence_content 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_fetch_payment_dispute_evidence_content call is checked against it from then on.
Questions about ebay_fetch_payment_dispute_evidence_content
Download evidence file content from a payment dispute.\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_fetch_payment_dispute_evidence_content: 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_fetch_payment_dispute_evidence_content 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_fetch_payment_dispute_evidence_content 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_fetch_payment_dispute_evidence_content. 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_fetch_payment_dispute_evidence_content 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