Delete a notification scheme. Irreversible.
AI agents call schemes.deleteNotificationScheme 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 permanently deletes a notification scheme, which is data destruction. Notification schemes are core Jira configuration used across projects; deleting one could disable critical notifications (issue updates, transitions, SLA breaches) for dependent projects.
From the tool's definition "Delete a notification scheme. Irreversible." The tool description explicitly states deletion and irreversibility, indicating a destructive operation that cannot be undone.
Attacks that exploit this kind of access
Delete a notification scheme. 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 schemes.deleteNotificationScheme: 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.
schemes.deleteNotificationScheme 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 schemes.deleteNotificationScheme 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 schemes.deleteNotificationScheme. 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.
schemes.deleteNotificationScheme 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 →