shellcheck
Runs ShellCheck (shell script linter) and returns structured diagnostics (file, line, column, rule, severity, message).
This record as markdown: /tools/io-github-dave-london-pare-test/shellcheck.md
What shellcheck does on Test
AI agents invoke shellcheck to trigger actions in Test. 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 shellcheck is rated High
The tool runs an external program (ShellCheck) on shell scripts. While it is read-only in intent (linting/analysis), it executes an external binary and processes arbitrary file inputs, placing it in the Execute category. Misuse could involve pointing it at unintended files or paths, but blast radius is moderate since it only reads and reports diagnostics without modifying files.
From the tool's definition 'Runs ShellCheck (shell script linter)' — actively executes an external process against a file
Attacks that exploit this kind of access
The rule that runs shellcheck safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Test, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For shellcheck, this is the rule to start with:
shellcheck 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 Test, apply this rule, and every shellcheck call is checked against it from then on.
Questions about shellcheck
Runs ShellCheck (shell script linter) and returns structured diagnostics (file, line, column, rule, severity, message). It is categorised as a Execute tool in the Test MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Test MCP server in PolicyLayer and add a rule for shellcheck: 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 Test. Nothing to install.
shellcheck 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 shellcheck 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 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.
shellcheck is provided by the Test 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 Test, and thousands of servers like it.
This server
Across the catalogue