Deactivate a discount (make it unusable without deleting).
AI agents use deactivate_discount to create or update resources in AdminAgent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AdminAgent environment.
This tool modifies discount configuration state in Shopify but does not destroy data or prevent reversal (can be reactivated). It is reversible Write operation. Severity is medium because disabling active discounts affects customer-facing promotions and revenue, but the impact can be undone by reactivation.
From the tool's definition Tool name 'deactivate_discount' and description 'Deactivate a discount (make it unusable without deleting)' indicates modifying the state of a discount resource reversibly—toggling its active status without permanent deletion.
Attacks that exploit this kind of access
Deactivate a discount (make it unusable without deleting). It is categorised as a Write tool in the AdminAgent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AdminAgent MCP server in PolicyLayer and add a rule for deactivate_discount: 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 AdminAgent. Nothing to install.
deactivate_discount 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 deactivate_discount 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 deactivate_discount. 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.
deactivate_discount is provided by the AdminAgent MCP server (rushikeshmore/admin-agent). 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 →