AI agents invoke add_chain_step 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.
Given the server context (Kali Linux security/pentesting tools) and sibling tools like 'adaptive_execute_strategy', 'ad_full_attack', 'adaptive_intelligent_orchestration', 'add_chain_step' likely adds a step to an attack/execution chain or workflow. This implies triggering or chaining security tool executions. Description is empty so confidence is lowered, but the most likely category given context is Execute.
From the tool's definition Tool name 'add_chain_step' on a server described as integrating 193 Kali Linux security tools for penetration testing; description is empty/uninformative.
Documented attack patterns abuse exactly the kind of access add_chain_step 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 add_chain_step:
{
"version": "1",
"default": "deny",
"tools": {
"add_chain_step": {
"limits": [
{
"counter": "add_chain_step_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}add_chain_step 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.
Free to start. No card required.
add_chain_step. 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 add_chain_step: 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.
add_chain_step 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 add_chain_step 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 add_chain_step. 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.
add_chain_step 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.