Get details of a specific marketing campaign by ID. Returns campaign configuration, status, and statistics.
AI agents call ebay_get_campaign 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.
This tool retrieves existing campaign information (configuration, status, statistics) by ID. It performs a query operation with no data modification, creation, deletion, code execution, or financial transaction. It is a straightforward read operation with minimal risk—the worst case would be exposure of campaign visibility/analytics data the user already owns.
From the tool's definition Tool name 'ebay_get_campaign' and description 'Get details of a specific marketing campaign by ID. Returns campaign configuration, status, and statistics.' indicate retrieval of campaign data without modification or side effects.
Documented attack patterns abuse exactly the kind of access ebay_get_campaign 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_campaign:
{
"version": "1",
"default": "deny",
"tools": {
"ebay_get_campaign": {}
}
}ebay_get_campaign is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get details of a specific marketing campaign by ID. Returns campaign configuration, status, and statistics. It is categorised as a Read tool in the Ebay MCP Server, which means it retrieves data without modifying state.
Register the Ebay MCP server in PolicyLayer and add a rule for ebay_get_campaign: 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_get_campaign 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_campaign 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_campaign. 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_campaign 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.
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.