AI agents use customfields.updateCustomField 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.
Updating a custom field in Jira is a reversible write operation that modifies configuration but does not delete data or execute arbitrary code. The blast radius is medium because misconfigured custom fields could disrupt project workflows, reporting, and issue tracking across teams, but the operation itself is not irreversible (updates can be reverted) and does not have financial implications.
From the tool's definition Tool name is "updateCustomField" and description states "Update a custom field". The verb "update" indicates modification of existing data.
Attacks that exploit this kind of access
Update a custom field. 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 customfields.updateCustomField: 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.
customfields.updateCustomField 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 customfields.updateCustomField 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 customfields.updateCustomField. 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.
customfields.updateCustomField 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 →