compare_runs
'It worked yesterday.' Give it the logs from the run that worked and the run that failed, and it isolates what actually changed between them instead of re-diagnosing the failure from scratch. Use this whenever a previously-green job starts failing.
This record as markdown: /tools/denpex-mcp/compare-runs.md
What compare_runs does on Denpex
AI agents invoke compare_runs to trigger actions in Denpex. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
failLogs | string | Yes | Logs from the run that failed. |
successLogs | string | Yes | Logs from the run that worked. |
Parameters from the server's own tool schema.
Why compare_runs is rated High
compare_runs triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs compare_runs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Denpex, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For compare_runs, this is the rule to start with:
compare_runs stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Denpex, apply this rule, and every compare_runs call is checked against it from then on.
Questions about compare_runs
'It worked yesterday.' Give it the logs from the run that worked and the run that failed, and it isolates what actually changed between them instead of re-diagnosing the failure from scratch. Use this whenever a previously-green job starts failing. It is categorised as a Execute tool in the Denpex MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
compare_runs accepts 2 parameters: failLogs, successLogs. Required: failLogs, successLogs. The full parameter table on this page comes from the server's own tool schema.
Register the Denpex MCP server in PolicyLayer and add a rule for compare_runs: 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 Denpex. Nothing to install.
compare_runs 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 compare_runs 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 compare_runs. 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.
compare_runs is provided by the Denpex MCP server (denpex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Denpex, and thousands of servers like it.
Across the catalogue