Lint a file using flake8 (Python) or eslint (JS).
AI agents call lint_file to retrieve information from Cursor MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Linting is a read-only static analysis operation that inspects code for errors and style issues without modifying any files or executing the code itself. It only reports findings, making it a Read category tool with low severity.
From the tool's definition Lint a file using flake8 (Python) or eslint (JS)
Attacks that exploit this kind of access
Lint a file using flake8 (Python) or eslint (JS). It is categorised as a Read tool in the Cursor MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cursor MCP Server MCP server in PolicyLayer and add a rule for lint_file: 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 Cursor MCP Server. Nothing to install.
lint_file is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the lint_file 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_file. 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_file is provided by the Cursor MCP Server MCP server (tariqnasheed/cursor_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 →