AI agents use schemes.updateNotificationScheme 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.
The tool updates notification scheme settings, which are reversible configuration changes affecting how users are notified of Jira events. This is a Write operation rather than Destructive (the scheme is not deleted, just modified). Severity is high because misconfigured notification schemes could suppress critical alerts or flood users with unwanted notifications, affecting organizational communication workflows.
From the tool's definition Tool name contains 'update' and description states 'Update a notification scheme.' This modifies an existing configuration object in Jira.
Attacks that exploit this kind of access
Update a notification scheme. 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 schemes.updateNotificationScheme: 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.updateNotificationScheme 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 schemes.updateNotificationScheme 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.updateNotificationScheme. 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.updateNotificationScheme 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 →