AI agents call ebay_search to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | Yes | Search query |
sort | string | — | Sort order (e.g. price, -price, newlyListed) |
limit | number | — | Results per page (max 200, default 20) |
filter | string | — | eBay filter string (e.g. price:[10..50]) |
offset | number | — | |
client_id | string | Yes | eBay application Client ID |
marketplace | string | — | Marketplace ID (default: EBAY_US) |
category_ids | string | — | Comma-separated category IDs |
client_secret | string | Yes | eBay application Client Secret |
Parameters from the server's own tool schema.
This tool retrieves and queries eBay listing data without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that returns search results. The severity is low because misuse would only result in unwanted queries, with no side effects, financial impact, or data loss.
From the tool's definition Tool name 'ebay_search' and description 'Search eBay listings via the Browse API' indicate a query/retrieval operation with no modification or execution of external code.
Attacks that exploit this kind of access
Search eBay listings via the Browse API. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
ebay_search accepts 9 parameters: q, sort, limit, filter, offset, client_id, marketplace, category_ids, client_secret. Required: q, client_id, client_secret. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for ebay_search: 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 UnClick. Nothing to install.
ebay_search 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_search 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_search. 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_search is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →