AI agents call automation.getAutomationUsage to retrieve information from Gojira without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns monitoring/telemetry data about Jira automation (execution counts, queue depth). It has no side effects, does not execute automations, and cannot modify any configuration or data. The read-only nature and limited information exposure (statistics only) justify a low severity rating.
From the tool's definition Tool name includes 'get' and description states it 'Returns automation usage statistics' — retrieves data about execution counts and queue depth with no modification of state.
Attacks that exploit this kind of access
Returns automation usage statistics for this site (executions, queue depth). It is categorised as a Read tool in the Gojira MCP Server, which means it retrieves data without modifying state.
Register the Gojira MCP server in PolicyLayer and add a rule for automation.getAutomationUsage: 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 Gojira. Nothing to install.
automation.getAutomationUsage 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 automation.getAutomationUsage 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 automation.getAutomationUsage. 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.
automation.getAutomationUsage is provided by the Gojira MCP server (windoze95/gojira-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 →