lint

What lint does on Cargo

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

Why lint is rated High

Linting tools like cargo clippy execute an external process/command against code. They don't modify data (Write) or delete anything (Destructive), but they do trigger execution of an external tool. The truncated description lowers confidence slightly, but given the context of a cargo operations server running clippy-style checks, Execute is the most appropriate category.

From the tool's definition Tool name 'lint' on a server that runs structured Rust cargo operations (build, test, clippy). The server description mentions 'clippy' which is a linting tool that executes code analysis. The description is truncated/uninformative ('Runs').

The rule that runs lint safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Cargo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lint, this is the rule to start with:

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

Questions about lint