Checks global SKU inventory across all fulfillment centers. Accepts either a skuId or productId — pass whichever you have.
AI agents call checkInventory to retrieve information from Bedrock Agent Core Operations Hub without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query operation to retrieve inventory status information. It accepts either a skuId or productId as input and returns inventory data across fulfillment centers. There are no side effects, no data modifications, no code execution, no deletions, and no financial transactions. This is a straightforward data retrieval operation, consistent with the 'Read' category.
From the tool's definition Tool name is 'checkInventory' and description states it 'Checks global SKU inventory across all fulfillment centers.' The verb 'checks' and the read-only nature of querying inventory data without modification indicates a retrieval operation.
Attacks that exploit this kind of access
Checks global SKU inventory across all fulfillment centers. Accepts either a skuId or productId — pass whichever you have. It is categorised as a Read tool in the Bedrock Agent Core Operations Hub MCP Server, which means it retrieves data without modifying state.
Register the Bedrock Agent Core Operations Hub MCP server in PolicyLayer and add a rule for checkInventory: 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 Bedrock Agent Core Operations Hub. Nothing to install.
checkInventory is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the checkInventory 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 checkInventory. 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.
checkInventory is provided by the Bedrock Agent Core Operations Hub MCP server (sujithpvarghese/bedrock-agent-core-operations-hub-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 →