commerce_create_ad
AI agents use commerce_create_ad to create or update resources in Commerce-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Commerce-MCP environment.
The tool creates new advertising data within the commerce system. This is a Write operation (creates new records reversibly). Severity is medium because misuse could create unwanted ad campaigns, waste marketing budget, or generate inappropriate content, but the effect is not financially binding without additional approval steps and can typically be undone.
From the tool's definition Tool name 'commerce_create_ad' indicates creation of advertising content. Sibling tools show this server manages e-commerce operations including 'advertising analytics'.
Attacks that exploit this kind of access
commerce_create_ad. It is categorised as a Write tool in the Commerce-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Commerce- MCP server in PolicyLayer and add a rule for commerce_create_ad: 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 Commerce-MCP. Nothing to install.
commerce_create_ad 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 commerce_create_ad 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 commerce_create_ad. 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.
commerce_create_ad is provided by the Commerce- MCP server (sinmb79/commerc-mcp). 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 →