Delete an automation rule. Irreversible.
AI agents call automation.deleteAutomationRule to permanently remove resources in Gojira — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes automation rules in Jira. Deletion of automation rules cannot be undone and constitutes a destructive action. The blast radius is high because removing automation rules can disrupt critical business workflows, notifications, and compliance-related automation in an organization's Jira instance.
From the tool's definition Tool name explicitly states 'deleteAutomationRule' and description marks it **Irreversible**, indicating permanent removal of data with no undo capability.
Attacks that exploit this kind of access
Delete an automation rule. Irreversible. It is categorised as a Destructive tool in the Gojira MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Gojira MCP server in PolicyLayer and add a rule for automation.deleteAutomationRule: 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.deleteAutomationRule is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the automation.deleteAutomationRule 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.deleteAutomationRule. 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.deleteAutomationRule 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 →