run_code_analysis
Static analysis on code or text content for security issues, secrets, homograph attacks, ANSI injections, suspicious URLs, and code quality. Returns structured findings with severity, line numbers, and remediation. Works on any text content — no file system access needed.
This record as markdown: /tools/io-github-homenshum-nodebench/run-code-analysis.md
What run_code_analysis does on Nodebench
AI agents invoke run_code_analysis 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_code_analysis is rated High
This tool runs static analysis execution on provided content. Although it does not modify data or delete anything, it actively executes analysis logic (pattern matching, AST parsing, regex checks for secrets/injections, etc.) on arbitrary text.
From the tool's definition Tool description states it performs 'Static analysis on code or text content' and 'Returns structured findings' — it executes analysis logic on arbitrary input.
Attacks that exploit this kind of access
The rule that runs run_code_analysis 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_code_analysis, this is the rule to start with:
run_code_analysis 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_code_analysis call is checked against it from then on.
Questions about run_code_analysis
Static analysis on code or text content for security issues, secrets, homograph attacks, ANSI injections, suspicious URLs, and code quality. Returns structured findings with severity, line numbers, and remediation. Works on any text content — no file system access needed. 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_code_analysis: 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_code_analysis 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_code_analysis 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_code_analysis. 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_code_analysis 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