AI agents use assets.updateObjectSchema 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 creates or modifies data (an object schema) reversibly. While schema updates can have wide blast radius (affecting all objects using that schema), they are not irreversible deletions and fit Write category. Severity is high because misconfigured schemas in a CMDB can cascade to many dependent records, and an agent error could corrupt asset tracking across the organization.
From the tool's definition Tool name includes 'update' and description states 'Update an object schema'. The Assets CMDB context indicates this modifies configuration that affects the entire asset database structure.
Attacks that exploit this kind of access
Update an object schema. 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 assets.updateObjectSchema: 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.updateObjectSchema 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 assets.updateObjectSchema 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.updateObjectSchema. 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.updateObjectSchema 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 →