Queries Jira for recent deployments or config changes that may have caused the issue.
AI agents call checkJiraCommits 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.
The tool retrieves historical information from Jira (commits, deployments, config changes) for diagnostic purposes. This is a passive information retrieval operation with no side effects, code execution, or data modification. Even in an autonomous agent context, querying deployment history poses minimal risk as it cannot alter infrastructure, execute commands, or cause destructive changes.
From the tool's definition Tool performs 'Queries Jira for recent deployments or config changes' — this is a read-only query operation with no modification or execution of external systems.
Attacks that exploit this kind of access
Queries Jira for recent deployments or config changes that may have caused the issue. 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 checkJiraCommits: 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.
checkJiraCommits 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 checkJiraCommits 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 checkJiraCommits. 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.
checkJiraCommits 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 →