schemes.deletePermissionScheme

Delete a permission scheme. Irreversible.

Server Gojira windoze95/gojira-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What schemes.deletePermissionScheme does on Gojira

AI agents call schemes.deletePermissionScheme 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.

Why schemes.deletePermissionScheme needs a policy

Permission schemes are foundational to Jira security and governance. Deleting one irreversibly removes access control rules, potentially disrupting project permissions, audit trails, and compliance posture. The word 'Irreversible' in the description confirms this cannot be undone. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.'

From the tool's definition Tool name explicitly states 'delete'; description explicitly states 'Irreversible.' This irreversibly removes a permission scheme, which controls access policies across Jira projects.

Questions about schemes.deletePermissionScheme

What does the schemes.deletePermissionScheme tool do? +

Delete a permission 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.

How do I enforce a policy on schemes.deletePermissionScheme? +

Register the Gojira MCP server in PolicyLayer and add a rule for schemes.deletePermissionScheme: 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.

What risk level is schemes.deletePermissionScheme? +

schemes.deletePermissionScheme is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit schemes.deletePermissionScheme? +

Yes. Add a rate_limit block to the schemes.deletePermissionScheme 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.

How do I block schemes.deletePermissionScheme completely? +

Set action: deny in the PolicyLayer policy for schemes.deletePermissionScheme. 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.

What MCP server provides schemes.deletePermissionScheme? +

schemes.deletePermissionScheme 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.