AI agents call shellcheck_scan to retrieve information from Kali Security MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Shellcheck performs static code analysis on shell scripts to identify bugs and potential issues. This is a read-only operation that examines code without modifying files or executing commands. No side effects occur. While the server integrates penetration testing tools, this specific tool is a diagnostic/analysis tool that does not execute code, modify systems, or delete data.
From the tool's definition Tool name 'shellcheck_scan' indicates static analysis of shell scripts; shellcheck is a well-known linter that inspects shell code for issues without executing it.
Documented attack patterns abuse exactly the kind of access shellcheck_scan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kali Security MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for shellcheck_scan:
{
"version": "1",
"default": "deny",
"tools": {
"shellcheck_scan": {}
}
}shellcheck_scan is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
shellcheck_scan. It is categorised as a Read tool in the Kali Security MCP MCP Server, which means it retrieves data without modifying state.
Register the Kali Security MCP server in PolicyLayer and add a rule for shellcheck_scan: 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 Kali Security MCP. Nothing to install.
shellcheck_scan is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the shellcheck_scan 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_scan. 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_scan is provided by the Kali Security MCP server (seac-25/kali-security-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 249 Kali Security MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
249 Kali Security MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.