AI agents use schemes.assignPermissionSchemeToProject 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.
This tool modifies project configuration by assigning a permission scheme, which changes access control rules for all project users. While the description states it is revertible, the act of assigning a new permission scheme has immediate side effects: it restructures who can perform what actions in the project. The change affects security posture and team permissions across the entire project.
From the tool's definition Assign a permission scheme to a project. Revertible (restore prior assignment).
Attacks that exploit this kind of access
Assign a permission scheme to a project. Revertible (restore prior assignment). 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.assignPermissionSchemeToProject: 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.assignPermissionSchemeToProject 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.assignPermissionSchemeToProject 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.assignPermissionSchemeToProject. 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.assignPermissionSchemeToProject 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 →