run_surface_chain
A execute tool on the Kali Security MCP server.
This record as markdown: /tools/seac-25-kali-security-mcp/run-surface-chain.md
What run_surface_chain does on Kali Security MCP
AI agents invoke run_surface_chain to trigger actions in Kali Security MCP. 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 run_surface_chain is rated High
Tool executes automated security workflows on Kali server; high blast radius without clear constraints on what surfaces or chains are targeted.
From the tool's definition uninformative description; 'run_surface_chain' suggests automated execution workflow on security testing server
Attacks that exploit this kind of access
The rule that runs run_surface_chain safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Kali Security MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_surface_chain, this is the rule to start with:
run_surface_chain 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 Kali Security MCP, apply this rule, and every run_surface_chain call is checked against it from then on.
Questions about run_surface_chain
run_surface_chain is a execute tool on the Kali Security MCP server. It is categorised as a Execute tool in the Kali Security MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali Security MCP server in PolicyLayer and add a rule for run_surface_chain: 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.
run_surface_chain 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 run_surface_chain 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 run_surface_chain. 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.
run_surface_chain 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.
More on Kali Security, and thousands of servers like it.
Across the catalogue