shellcheck_script · Code Review MCP: Risk & Policy

WHAT IT DOES

What shellcheck_script does on Code Review

AI agents invoke shellcheck_script to trigger actions in Code Review. 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 IT NEEDS A POLICY

Why shellcheck_script needs a policy

ShellCheck is a static analysis tool that examines Bash scripts for potential issues. While the tool itself is non-destructive and read-only in its operation (it analyzes code without modifying or deleting it), it still falls under Execute because it triggers an external program/subprocess execution.

From the tool's definition Tool name 'shellcheck_script' and description 'Runs ShellCheck on a Bash script' indicates execution of an external analysis tool (ShellCheck) on user-provided script content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

shellcheck_script Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Code Review, so you can run agents against it safely.

FAQ

Questions about shellcheck_script

What does the shellcheck_script tool do? +

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

How do I enforce a policy on shellcheck_script? +

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

What risk level is shellcheck_script? +

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

Can I rate-limit shellcheck_script? +

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

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

shellcheck_script is provided by the Code Review MCP server (troshenkov/code-review-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.