AI agents call orgAdmin.getOrgPolicies 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 is a Read operation—it retrieves organizational policies without side effects. Severity is medium rather than low because the exposed data (data residency settings, IP allowlists, security policies) could be sensitive and useful for reconnaissance if leaked to an attacker. An AI agent with this access could enumerate security configurations but cannot modify them.
From the tool's definition Tool name contains 'get' and description states 'List org policies'; both indicate data retrieval with no modification or execution. However, org policies including 'data residency' and 'IP allowlists' are security-sensitive configuration data.
Attacks that exploit this kind of access
List org policies (data residency, IP allowlists, etc.). 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 orgAdmin.getOrgPolicies: 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.
orgAdmin.getOrgPolicies 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 orgAdmin.getOrgPolicies 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 orgAdmin.getOrgPolicies. 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.
orgAdmin.getOrgPolicies 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 →