AI agents invoke lint_files 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.
This tool executes linting rules (external code/logic) on project files. Although linting is typically a read-heavy analysis operation, the 'Run' verb combined with 'custom linting rules' indicates active execution of external rule logic. The severity is medium rather than high because linting is a non-destructive, analysis-focused operation that does not modify or delete files.
From the tool's definition Tool description states 'Run custom linting rules on project files' — the verb 'Run' indicates execution of linting rules against files, which is a code execution operation with externally-dependent outcomes based on which files and rules are targeted.
Documented attack patterns abuse exactly the kind of access lint_files 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 lint_files:
{
"version": "1",
"default": "deny",
"tools": {
"lint_files": {
"limits": [
{
"counter": "lint_files_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}lint_files 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 custom linting rules on project files. 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 lint_files: 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.
lint_files 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 lint_files 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 lint_files. 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.
lint_files 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.