Checks if a previous sync job failed and left a message in the DLQ.
AI agents call checkDeadLetterQueue 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 read-only diagnostic check of queue status. It retrieves information about failed sync jobs and their messages but does not modify state, execute external operations, delete data, or commit financial transactions. The blast radius of misuse is minimal—an agent querying this repeatedly would at worst cause log spam or minor resource consumption, not operational damage or data loss.
From the tool's definition Tool name 'checkDeadLetterQueue' and description 'Checks if a previous sync job failed and left a message in the DLQ' indicate a query operation that retrieves status information from a dead-letter queue without modifying or executing operations.
Attacks that exploit this kind of access
Checks if a previous sync job failed and left a message in the DLQ. 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 checkDeadLetterQueue: 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.
checkDeadLetterQueue 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 checkDeadLetterQueue 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 checkDeadLetterQueue. 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.
checkDeadLetterQueue 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 →