This record as markdown: /tools/io-github-dave-london-pare-search/lint.md
What lint does on Search
AI agents invoke lint to trigger actions in Search. 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
A lint tool runs an external program or script against code, which constitutes executing an operation with side effects beyond simple data retrieval. The description is truncated ('Runs') but the context of a code operations server and the tool name strongly imply execution of a linter process. Confidence is moderate due to the incomplete description.
From the tool's definition Tool name is 'lint' on a server described as running structured code operations (ripgrep + fd); 'Runs' suggests execution of an external linting process
Attacks that exploit this kind of access
The rule that runs lint safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Search, 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:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Search, apply this rule, and every lint call is checked against it from then on.
Questions about lint
Runs. It is categorised as a Execute tool in the Search MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Search 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 Search. Nothing to install.
lint 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 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. 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 is provided by the Search MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Search, and thousands of servers like it.
Across the catalogue