Remove a reference between two Assets objects.
AI agents call assets.removeObjectReference 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.
Removing an object reference in an Assets CMDB is a destructive operation: the link between two objects is deleted and cannot be easily recovered without audit logs or manual re-creation. In a CMDB context, broken references can impact dependency tracking, incident management, and configuration integrity, making the blast radius high.
From the tool's definition 'Remove a reference between two Assets objects' — removing a reference is an irreversible deletion of a relationship between CMDB objects
Attacks that exploit this kind of access
Remove a reference between two Assets objects. 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.
Register the Gojira MCP server in PolicyLayer and add a rule for assets.removeObjectReference: 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.
assets.removeObjectReference is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the assets.removeObjectReference 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 assets.removeObjectReference. 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.
assets.removeObjectReference 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 →