adjust_inventory
AI agents use adjust_inventory 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.
Adjusting inventory creates or modifies quantity records in a Shopify store—a Write operation. It is reversible (can be adjusted again) and does not permanently delete data, so it is not Destructive. The severity is medium because incorrect inventory adjustments can disrupt order fulfillment and customer experience, but the impact is scoped to inventory records and is correctable.
From the tool's definition Tool name 'adjust_inventory' indicates modification of inventory quantities. The parent server description mentions 'bulk operations' and 'full store management', and sibling tools include 'activate_inventory_at_location' and 'cancel_bulk_operation',…
Attacks that exploit this kind of access
adjust_inventory. 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 adjust_inventory: 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.
adjust_inventory 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 adjust_inventory 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 adjust_inventory. 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.
adjust_inventory 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 →