ebay_delete_notification_destination
Delete a notification destination
This record as markdown: /tools/yosefhayim-ebay-mcp/ebay-delete-notification-destination.md
What ebay_delete_notification_destination does on Ebay
AI agents call ebay_delete_notification_destination to permanently remove resources in Ebay, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why ebay_delete_notification_destination is rated Critical
The tool permanently deletes a notification destination configuration, which cannot be easily undone. While not directly financial or data-destructive in scale, removing notification infrastructure could disrupt critical seller operations (order alerts, payment notifications, dispute updates). This qualifies as Destructive because deletion is irreversible.
From the tool's definition Tool name contains 'delete' and description states 'Delete a notification destination' — this irreversibly removes a configured destination for eBay notifications.
Attacks that exploit this kind of access
The rule that runs ebay_delete_notification_destination 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_delete_notification_destination, this is the rule to start with:
ebay_delete_notification_destination is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ebay, apply this rule, and every ebay_delete_notification_destination call is checked against it from then on.
Questions about ebay_delete_notification_destination
Delete a notification destination. It is categorised as a Destructive tool in the Ebay MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ebay MCP server in PolicyLayer and add a rule for ebay_delete_notification_destination: 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_delete_notification_destination is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the ebay_delete_notification_destination 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_delete_notification_destination. 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_delete_notification_destination 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.
Across the catalogue