Run ruff linter on specified files. Useful to check that nothing was broken.
AI agents invoke ruff_check to trigger actions in MCP File System 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 runs an external process (ruff linter) on files, making it an Execute category action. While ruff is read-only in nature (it only checks code without modifying it by default), it still executes an external command whose behavior depends on arguments and configuration.
From the tool's definition "Run ruff linter on specified files" — actively executes an external linter process against specified files
Attacks that exploit this kind of access
Run ruff linter on specified files. Useful to check that nothing was broken. It is categorised as a Execute tool in the MCP File System Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP File System Server MCP server in PolicyLayer and add a rule for ruff_check: 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 File System Server. Nothing to install.
ruff_check 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 ruff_check 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 ruff_check. 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.
ruff_check is provided by the MCP File System Server MCP server (kvas-it/mcp-server-fs). 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 →