AI agents invoke nodejs_lint to trigger actions in MCP DevTools Server. 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.
ESLint is a code analysis tool that executes linting rules against source files. While primarily a read-only analysis tool by default, ESLint has the capability to modify files (via --fix) and execute custom rules/plugins (arbitrary code). The execution of external tools and potential for side effects beyond simple reading places this in the Execute category rather than Read.
From the tool's definition Tool description states "Run ESLint on Node.js/TypeScript code" - the verb 'Run' indicates execution of an external linter tool. ESLint execution can have side effects including file modifications (with --fix flag), and executing arbitrary configuration code.
Documented attack patterns abuse exactly the kind of access nodejs_lint gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP DevTools Server, and nothing reaches the server without passing your rules. This is the rule we recommend for nodejs_lint:
{
"version": "1",
"default": "deny",
"tools": {
"nodejs_lint": {
"limits": [
{
"counter": "nodejs_lint_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}nodejs_lint 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.
Free to start. No card required.
Run ESLint on Node.js/TypeScript code. It is categorised as a Execute tool in the MCP DevTools Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP DevTools Server MCP server in PolicyLayer and add a rule for nodejs_lint: 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 MCP DevTools Server. Nothing to install.
nodejs_lint 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 nodejs_lint 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 nodejs_lint. 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.
nodejs_lint is provided by the MCP DevTools Server MCP server (rshade/mcp-devtools-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP DevTools Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
79 MCP DevTools Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.