AI agents use jsm.setRequestTypeFields 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 JSM request type field configurations, which affects how requests are structured organization-wide but does not delete data or execute arbitrary code. The blast radius is medium because misconfiguration could disrupt request workflows and data collection across service management processes, but the change is reversible and scoped to schema/configuration rather than instance data.
From the tool's definition "Replace the field set on a request type" — this modifies JSM request type configuration, altering which fields are associated with a request type. The action is reversible (can be replaced again with different fields).
Attacks that exploit this kind of access
Replace the field set on a request type. 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 jsm.setRequestTypeFields: 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.
jsm.setRequestTypeFields 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 jsm.setRequestTypeFields 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 jsm.setRequestTypeFields. 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.
jsm.setRequestTypeFields 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 →