trigger_investigation
When an eval run shows regression, trigger a new verification cycle to investigate. This is how the outer loop feeds the inner loop: regressions trigger 6-phase investigations.
This record as markdown: /tools/io-github-homenshum-nodebench/trigger-investigation.md
What trigger_investigation does on Nodebench
AI agents invoke trigger_investigation to trigger actions in Nodebench. 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.
Why trigger_investigation is rated High
This tool triggers external operations (investigation cycles, verification phases) whose effects are not immediately reversible and depend on runtime arguments. It does not read data passively, create reversible modifications, delete data, nor move money. The 'trigger' verb and reference to multi-phase investigation cycles indicate active orchestration of dependent processes, fitting the Execute category.
From the tool's definition Tool description states 'trigger a new verification cycle' and 'regressions trigger 6-phase investigations' — these actions initiate automated processes whose side effects depend on which regression is selected and what the verification cycle executes.
Attacks that exploit this kind of access
The rule that runs trigger_investigation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For trigger_investigation, this is the rule to start with:
trigger_investigation 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 Nodebench, apply this rule, and every trigger_investigation call is checked against it from then on.
Questions about trigger_investigation
When an eval run shows regression, trigger a new verification cycle to investigate. This is how the outer loop feeds the inner loop: regressions trigger 6-phase investigations. It is categorised as a Execute tool in the Nodebench MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nodebench MCP server in PolicyLayer and add a rule for trigger_investigation: 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 Nodebench. Nothing to install.
trigger_investigation 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 trigger_investigation 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 trigger_investigation. 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.
trigger_investigation is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
Across the catalogue