AI agents call workflows.getWorkflowConditions 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 and retrieves workflow transition conditions, which is a read-only operation with no side effects. It does not create, modify, delete, or execute any actions—it simply returns configuration information about existing workflows. The low severity reflects minimal blast radius if misused by an agent, as reading workflow conditions poses no risk of data loss, financial impact, or unintended execution.
From the tool's definition Tool name 'getWorkflowConditions' and description 'Get the conditions for a workflow transition' indicate retrieval of existing workflow configuration data with no modification or execution.
Attacks that exploit this kind of access
Get the conditions 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.getWorkflowConditions: 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.getWorkflowConditions 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.getWorkflowConditions 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.getWorkflowConditions. 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.getWorkflowConditions 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 →