Create or replace SKU location mapping for a listing. Maps a SKU to multiple fulfillment center locations.\n\nRequired OAuth Scope: sell.inventory\nMinimum Scope: https://api.ebay.com/oauth/api_scope/sell.inventory
How to control ebay_create_or_replace_sku_location_mapping ↓
AI agents use ebay_create_or_replace_sku_location_mapping to create or update resources in Ebay — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ebay environment.
This tool modifies inventory data by mapping SKUs to fulfillment center locations. While it creates/updates configuration data (Write category), the blast radius is medium rather than high because: (1) these are mappings that can be corrected/undone, (2) the impact is limited to inventory routing/location configuration rather than order fulfillment or financial transactions, and (3) the OAuth scope is restricted to…
From the tool's definition Tool creates or replaces SKU location mapping data for inventory management. The description explicitly states 'Create or replace' which indicates reversible modification of inventory configuration data.
Documented attack patterns abuse exactly the kind of access ebay_create_or_replace_sku_location_mapping 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_create_or_replace_sku_location_mapping:
{
"version": "1",
"default": "deny",
"tools": {
"ebay_create_or_replace_sku_location_mapping": {
"limits": [
{
"counter": "ebay_create_or_replace_sku_location_mapping_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}ebay_create_or_replace_sku_location_mapping stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create or replace SKU location mapping for a listing. Maps a SKU to multiple fulfillment center locations.\n\nRequired OAuth Scope: sell.inventory\nMinimum Scope: https://api.ebay.com/oauth/api_scope/sell.inventory. It is categorised as a Write tool in the Ebay MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ebay MCP server in PolicyLayer and add a rule for ebay_create_or_replace_sku_location_mapping: 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_create_or_replace_sku_location_mapping is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ebay_create_or_replace_sku_location_mapping 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_create_or_replace_sku_location_mapping. 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_create_or_replace_sku_location_mapping 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.