Critical Risk →

ebay_delete_notification_destination

Delete a notification destination

How to control ebay_delete_notification_destination ↓

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.

Critical Risk

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.

Documented attack patterns abuse exactly the kind of access ebay_delete_notification_destination 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_delete_notification_destination:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "ebay_delete_notification_destination"
  ]
}

ebay_delete_notification_destination disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Ebay — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the ebay_delete_notification_destination tool do? +

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.

How do I enforce a policy on ebay_delete_notification_destination? +

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.

What risk level is ebay_delete_notification_destination? +

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.

Can I rate-limit ebay_delete_notification_destination? +

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.

How do I block ebay_delete_notification_destination completely? +

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.

What MCP server provides ebay_delete_notification_destination? +

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.

Enforce policy on every Ebay tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.