Run project lint command
AI agents invoke run_lint to trigger actions in Coding MCP 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.
This tool executes a project's lint command, which runs code analysis tools. While linting is generally safe compared to arbitrary command execution, it still executes external processes and could potentially trigger unintended side effects if lint configurations are malicious or if the linting tool itself has vulnerabilities.
From the tool's definition Tool name 'run_lint' and description 'Run project lint command' indicate execution of a linting command. The server description emphasizes 'safe command execution,' and this tool triggers external operations (linting scripts) whose behavior depends on project…
Attacks that exploit this kind of access
Run project lint command. It is categorised as a Execute tool in the Coding MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Coding MCP Server MCP server in PolicyLayer and add a rule for run_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 Coding MCP Server. Nothing to install.
run_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 run_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 run_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.
run_lint is provided by the Coding MCP Server MCP server (kieutrongthien/coding-mcp). 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 →