Create a new product (item) in the shop. Expects full item payload per Shopee /product/add_item spec (category_id, item_name, description, price+stock via model list or tier_variation, image.image_id_list, weight, logistic_info, etc.).
AI agents use add_item to create or update resources in Mcp Ap2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Ap2 environment.
This tool creates new product data in a shop system, which is a data modification action. It is reversible (products can be updated or removed later), so it falls under Write rather than Destructive. The severity is medium because misuse could populate the shop with fraudulent or spam products, but the impact is limited to shop inventory and can be corrected.
From the tool's definition Tool description states 'Create a new product (item) in the shop' with payload details like category_id, item_name, description, price, stock, images, weight, and logistics.
Documented attack patterns abuse exactly the kind of access add_item gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for add_item:
{
"version": "1",
"default": "deny",
"tools": {
"add_item": {
"limits": [
{
"counter": "add_item_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_item 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 a new product (item) in the shop. Expects full item payload per Shopee /product/add_item spec (category_id, item_name, description, price+stock via model list or tier_variation, image.image_id_list, weight, logistic_info, etc.). It is categorised as a Write tool in the Mcp Ap2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for add_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 Mcp Ap2. Nothing to install.
add_item 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 add_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 add_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.
add_item is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.