run_tests_cli
Execute a shell test command with timeout, capture stdout/stderr, and return structured results. Useful for running test suites, linters, or build commands as part of verification workflows.
This record as markdown: /tools/io-github-homenshum-nodebench/run-tests-cli.md
What run_tests_cli does on Nodebench
AI agents invoke run_tests_cli 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 run_tests_cli is rated High
The tool explicitly executes shell commands, which is Execute category. Severity is high because shell command execution has broad blast radius—an agent could run arbitrary commands beyond tests (e.g., rm -rf, curl exfiltration, privilege escalation). The timeout and structured output don't eliminate the underlying risk.
From the tool's definition Execute a shell test command with timeout, capture stdout/stderr, and return structured results. Useful for running test suites, linters, or build commands.
Attacks that exploit this kind of access
The rule that runs run_tests_cli 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 run_tests_cli, this is the rule to start with:
run_tests_cli 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 run_tests_cli call is checked against it from then on.
Questions about run_tests_cli
Execute a shell test command with timeout, capture stdout/stderr, and return structured results. Useful for running test suites, linters, or build commands as part of verification workflows. 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 run_tests_cli: 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.
run_tests_cli 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 run_tests_cli 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 run_tests_cli. 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.
run_tests_cli 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