Queries the RAG troubleshooting guide for a known resolution to an error code. Call this before retrying a failed sync.
AI agents call queryGuide 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 lookup/search operation against a knowledge base (RAG system) to retrieve troubleshooting information. It retrieves existing data without modifying, deleting, executing code, moving money, or triggering external operations. The query action is purely informational and read-only in nature.
From the tool's definition Tool name 'queryGuide' and description 'Queries the RAG troubleshooting guide for a known resolution to an error code' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Queries the RAG troubleshooting guide for a known resolution to an error code. Call this before retrying a failed sync. 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 queryGuide: 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.
queryGuide 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 queryGuide 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 queryGuide. 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.
queryGuide 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 →