This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/ebay-get-item.md
What ebay_get_item does on UnClick
AI agents call ebay_get_item to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
item_id | string | Yes | eBay item ID (e.g. v1|123456789|0) |
client_id | string | Yes | |
fieldgroups | string | — | |
marketplace | string | — | |
client_secret | string | Yes |
Parameters from the server's own tool schema.
Why ebay_get_item is rated Low
This tool retrieves and queries eBay item data without modifying, deleting, or executing any operations. It has minimal blast radius—an agent using it can only view publicly available item information. No financial transactions, data modification, or destructive actions are performed.
From the tool's definition Tool name 'ebay_get_item' and description 'Get full details for an eBay item by item ID' indicate a retrieval operation with no side effects. The verb 'get' and the read-only nature of fetching item details confirm this is a query operation.
Attacks that exploit this kind of access
The rule that runs ebay_get_item safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ebay_get_item, this is the rule to start with:
ebay_get_item 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 UnClick, apply this rule, and every ebay_get_item call is checked against it from then on.
Questions about ebay_get_item
Get full details for an eBay item by item ID. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
ebay_get_item accepts 5 parameters: item_id, client_id, fieldgroups, marketplace, client_secret. Required: item_id, 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_get_item: 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_get_item 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_item 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_item. 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_item 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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue