AI agents call schemes.getPermissionScheme to retrieve information from Gojira without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns permission scheme data from Atlassian Jira without modifying, deleting, or executing operations. It is a straightforward read operation that retrieves configuration information. The low severity reflects minimal blast radius—even if an AI agent misuses this tool, it only exposes existing permission configurations without side effects.
From the tool's definition Tool name contains 'get' and description indicates it retrieves a single permission scheme with its grant list. The verb 'Get' and 'retrieve' semantics confirm read-only data access with no modifications.
Attacks that exploit this kind of access
Get a single permission scheme (with full grant list when expand=. It is categorised as a Read tool in the Gojira MCP Server, which means it retrieves data without modifying state.
Register the Gojira MCP server in PolicyLayer and add a rule for schemes.getPermissionScheme: 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.getPermissionScheme is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the schemes.getPermissionScheme 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.getPermissionScheme. 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.getPermissionScheme 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 →