Run ESLint on JavaScript/TypeScript code and return analysis results.
AI agents invoke eslint_script to trigger actions in Code Review. 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.
This is an Execute category tool because it runs a code analysis tool (ESLint) whose behavior depends on the configuration and the code being analyzed. While ESLint's primary purpose is static analysis (not destructive), the execution of external processes with variable inputs and potential plugin execution means it fits Execute rather than Read.
From the tool's definition The tool name 'eslint_script' combined with the description 'Run ESLint on JavaScript/TypeScript code' indicates the tool executes an external linting process on user-provided code.
Attacks that exploit this kind of access
Run ESLint on JavaScript/TypeScript code and return analysis results. It is categorised as a Execute tool in the Code Review MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Code Review MCP server in PolicyLayer and add a rule for eslint_script: 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 Code Review. Nothing to install.
eslint_script 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 eslint_script 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 eslint_script. 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.
eslint_script is provided by the Code Review MCP server (troshenkov/code-review-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →