Checks the live web system for product sellability status. Always call this FIRST.
AI agents call checkWebDatabase 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 retrieves or queries data about product sellability status from a database. The verb 'checks' and the passive framing ('for status') indicate information retrieval only. There is no indication of data creation, modification, deletion, code execution, or financial impact.
From the tool's definition Tool name 'checkWebDatabase' and description 'Checks the live web system for product sellability status' indicate a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Checks the live web system for product sellability status. Always call this FIRST. 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 checkWebDatabase: 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.
checkWebDatabase 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 checkWebDatabase 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 checkWebDatabase. 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.
checkWebDatabase 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 →