High Risk →

lint

Runs

How to control lint ↓

What lint does on Make

AI agents invoke lint to trigger actions in Make. 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.

High Risk

Why lint needs a policy

Lint tools execute a static analysis process against code or files. On a Make/Just task runner server, this triggers an external command/script execution. While typically read-only in effect, it runs arbitrary task-runner targets which could have side effects depending on configuration.

From the tool's definition Tool name 'lint' combined with server description 'MCP server for Make/Just task runners' — runs a lint task via Make/Just task runner

Documented attack patterns abuse exactly the kind of access lint gives an agent:

How to control lint

PolicyLayer is an MCP gateway — it sits between your AI agents and Make, and nothing reaches the server without passing your rules. This is the rule we recommend for lint:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "lint": {
      "limits": [
        {
          "counter": "lint_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

lint 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.

  1. Create a free account and register Make — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about lint

What does the lint tool do? +

Runs. It is categorised as a Execute tool in the Make MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on lint? +

Register the Make MCP server in PolicyLayer and add a rule for 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 Make. Nothing to install.

What risk level is lint? +

lint is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit lint? +

Yes. Add a rate_limit block to the 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.

How do I block lint completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides lint? +

lint is provided by the Make MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Make tool call.

Start from Make, 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.

202 Make tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.