Update existing evidence in a payment dispute.\n\nRequired OAuth Scope: sell.fulfillment\nMinimum Scope: https://api.ebay.com/oauth/api_scope/sell.fulfillment
AI agents use ebay_update_payment_dispute_evidence 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.
This tool modifies existing payment dispute evidence, which is reversible (evidence can be updated again or removed), placing it in the Write category rather than Destructive. However, the severity is high because tampering with payment dispute evidence could be used to fraudulently influence dispute outcomes, potentially resulting in financial loss, unauthorized payment reversals, or eBay account sanctions.
From the tool's definition Tool name indicates 'update' operation on 'payment dispute evidence', which modifies existing data. Description explicitly states 'Update existing evidence in a payment dispute.' The OAuth scope 'sell.fulfillment' permits modifications to fulfillment and…
Documented attack patterns abuse exactly the kind of access ebay_update_payment_dispute_evidence gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ebay, and nothing reaches the server without passing your rules. This is the rule we recommend for ebay_update_payment_dispute_evidence:
{
"version": "1",
"default": "deny",
"tools": {
"ebay_update_payment_dispute_evidence": {
"limits": [
{
"counter": "ebay_update_payment_dispute_evidence_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}ebay_update_payment_dispute_evidence 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.
Free to start. No card required.
Update existing evidence in 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 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_update_payment_dispute_evidence: 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_update_payment_dispute_evidence 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_update_payment_dispute_evidence 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_update_payment_dispute_evidence. 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_update_payment_dispute_evidence 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.
Deterministic rules across all 332 Ebay tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
332 Ebay tools catalogued and risk-classified — across an index of 42,500+ MCP servers.