Low Risk

ebay_get_notification_destinations

Get all notification destinations (paginated)

How to control ebay_get_notification_destinations ↓

AI agents call ebay_get_notification_destinations to retrieve information from Ebay without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves notification destination configuration data without side effects. It is a simple query operation that returns existing data in paginated format. No data is created, modified, deleted, or used to trigger external operations. This is a straightforward Read category tool with low severity since notification destination information is not sensitive operational data.

From the tool's definition Tool name contains 'get' and description states 'Get all notification destinations (paginated)' — a retrieval operation with no modification or deletion of data.

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "ebay_get_notification_destinations": {}
  }
}

ebay_get_notification_destinations is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  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.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the ebay_get_notification_destinations tool do? +

Get all notification destinations (paginated). It is categorised as a Read tool in the Ebay MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ebay_get_notification_destinations? +

Register the Ebay MCP server in PolicyLayer and add a rule for ebay_get_notification_destinations: 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_get_notification_destinations? +

ebay_get_notification_destinations is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ebay_get_notification_destinations? +

Yes. Add a rate_limit block to the ebay_get_notification_destinations 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_get_notification_destinations completely? +

Set action: deny in the PolicyLayer policy for ebay_get_notification_destinations. 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_get_notification_destinations? +

ebay_get_notification_destinations 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.