AI agents call workflows.getWorkflowValidators 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 tool queries configuration data (validators) for a workflow transition in Jira. It is a read-only operation that retrieves existing validation rules without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal—an attacker could only learn about workflow validation configuration, which is informational rather than operationally damaging.
From the tool's definition Tool name 'getWorkflowValidators' and description 'Get the validators for a workflow transition' indicate a retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
Get the validators for a workflow transition. 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 workflows.getWorkflowValidators: 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.
workflows.getWorkflowValidators 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 workflows.getWorkflowValidators 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 workflows.getWorkflowValidators. 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.
workflows.getWorkflowValidators 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 →