AI agents invoke evaluate to trigger actions in Run Iq. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Although described as 'dry-run mode' (suggesting no side effects), the tool executes arbitrary rules and plugins against user-supplied data. The severity is medium rather than high because: (1) dry-run mode implies no persistent state changes, (2) the blast radius depends on what plugins/rules are available, and (3) there is no indication of irreversible data deletion or financial operations.
From the tool's definition The tool 'evaluate' processes input data through a parametric policy engine with dynamic plugin support, returning computed values, rule breakdowns, and execution traces.
Attacks that exploit this kind of access
Evaluate Run-IQ rules against input data in dry-run mode. Returns the computed value, breakdown per rule, applied/skipped rules, and execution trace. It is categorised as a Execute tool in the Run Iq MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Run Iq MCP server in PolicyLayer and add a rule for evaluate: 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 Run Iq. Nothing to install.
evaluate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the evaluate 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 evaluate. 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.
evaluate is provided by the Run Iq MCP server (run-iq/mcp-server). 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 →