Low Risk

shellcheck

Runs ShellCheck (shell script linter) and returns structured diagnostics (file, line, column, rule, severity, message).

Accepts file system path (path); Accepts freeform code/query input (shell); High parameter count (13 properties)

Part of the Lint MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@paretools/lint Read Risk 2/5

AI agents call shellcheck to retrieve information from Lint without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though shellcheck only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-dave-london-lint.yaml
tools:
  shellcheck:
    rules:
      - action: allow

See the full Lint policy for all 9 tools.

Tool Name shellcheck
Category Read
MCP Server Lint MCP Server
Risk Level Low

View all 9 tools →

Agents calling read-class tools like shellcheck have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the shellcheck tool do? +

Runs ShellCheck (shell script linter) and returns structured diagnostics (file, line, column, rule, severity, message).. It is categorised as a Read tool in the Lint MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on shellcheck? +

Add a rule in your Intercept YAML policy under the tools section for shellcheck. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Lint MCP server.

What risk level is shellcheck? +

shellcheck is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit shellcheck? +

Yes. Add a rate_limit block to the shellcheck rule in your Intercept 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 shellcheck completely? +

Set action: deny in the Intercept policy for shellcheck. 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 shellcheck? +

shellcheck is provided by the Lint MCP server (@paretools/lint). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Lint

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.