ebay_get_cancellation_requests
Scan recent seller orders for cancellation requests. Calls Fulfillment API getOrders and returns orders whose cancelState is not NONE_REQUESTED (or that list cancel requests). Read-only helper — does not use the deprecated Post-Order API.\n\nRequired OAuth Scope: sell.fulfillment.readonly or sell...
This record as markdown: /tools/yosefhayim-ebay-mcp/ebay-get-cancellation-requests.md
What ebay_get_cancellation_requests does on Ebay
AI agents call ebay_get_cancellation_requests 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_cancellation_requests is rated Low
This tool retrieves and queries cancellation request data from seller orders without creating, modifying, or deleting any data. It has no side effects beyond data retrieval, making it a straightforward Read operation. The blast radius is minimal since it only exposes existing order information the seller can already access.
From the tool's definition Tool description explicitly states 'Read-only helper — does not use the deprecated Post-Order API' and 'Scan recent seller orders for cancellation requests.' It calls Fulfillment API getOrders and returns data without modification.
Attacks that exploit this kind of access
The rule that runs ebay_get_cancellation_requests 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_cancellation_requests, this is the rule to start with:
ebay_get_cancellation_requests 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_cancellation_requests call is checked against it from then on.
Questions about ebay_get_cancellation_requests
Scan recent seller orders for cancellation requests. Calls Fulfillment API getOrders and returns orders whose cancelState is not NONE_REQUESTED (or that list cancel requests). Read-only helper — does not use the deprecated Post-Order API.\n\nRequired OAuth Scope: sell.fulfillment.readonly or sell.fulfillment\nMinimum Scope: https://api.ebay.com/oauth/api_scope/sell.fulfillment.readonly. 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_cancellation_requests: 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_cancellation_requests 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_cancellation_requests 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_cancellation_requests. 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_cancellation_requests 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