ebay_get_listing_violations
DECOMMISSIONED: eBay shut down the Sell Compliance API on 2026-03-30. This tool always fails with a clear message. Use Seller Hub → Performance → Issue Resolution Center instead (no API equivalent).
This record as markdown: /tools/yosefhayim-ebay-mcp/ebay-get-listing-violations.md
What ebay_get_listing_violations does on Ebay
AI agents call ebay_get_listing_violations 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_listing_violations is rated Low
Although the tool is non-functional due to decommissioning, its intended purpose is to retrieve listing violation information (a read operation with no side effects). The fact that it is decommissioned and fails safely means there is minimal risk if called. Severity is low because the tool cannot execute any operations.
From the tool's definition Tool name 'ebay_get_listing_violations' indicates retrieval/query of violation data. Description states the tool is 'DECOMMISSIONED' and 'always fails', meaning it performs no actual operation.
Attacks that exploit this kind of access
The rule that runs ebay_get_listing_violations 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_listing_violations, this is the rule to start with:
ebay_get_listing_violations 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_listing_violations call is checked against it from then on.
Questions about ebay_get_listing_violations
DECOMMISSIONED: eBay shut down the Sell Compliance API on 2026-03-30. This tool always fails with a clear message. Use Seller Hub → Performance → Issue Resolution Center instead (no API equivalent). 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_listing_violations: 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_listing_violations 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_listing_violations 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_listing_violations. 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_listing_violations 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