AI agents use automation.updateAutomationRule to create or update resources in Gojira — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gojira environment.
This tool modifies an existing Jira automation rule by replacing its body. While reversible (the diff is captured, implying rollback potential), automation rules can trigger broad downstream effects if misconfigured, making misuse high severity. It is a Write operation since it updates existing data rather than executing code or deleting anything.
From the tool's definition 'Replace a rule body in place' and 'Captures full-before/full-after diff' indicate an in-place update of an automation rule, which is a reversible write operation.
Attacks that exploit this kind of access
Replace a rule body in place. Captures full-before/full-after diff. It is categorised as a Write tool in the Gojira MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gojira MCP server in PolicyLayer and add a rule for automation.updateAutomationRule: 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.updateAutomationRule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the automation.updateAutomationRule 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.updateAutomationRule. 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.updateAutomationRule 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 →