AI agents invoke workflow_execute 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.
This tool executes security testing workflows within the Kali Linux framework. While labeled as a security tool, from an AI safety perspective, workflow_execute has critical blast radius: an AI agent given access could automatically trigger penetration tests, SQL injection attempts, command injection tests, and network attacks against systems without proper authorization or human oversight.
From the tool's definition Tool name 'workflow_execute' combined with description '执行测试工作流' (Execute test workflow) in the Kali Security MCP context indicates execution of automated penetration testing workflows.
Documented attack patterns abuse exactly the kind of access workflow_execute 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 workflow_execute:
{
"version": "1",
"default": "deny",
"tools": {
"workflow_execute": {
"limits": [
{
"counter": "workflow_execute_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}workflow_execute 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.
执行测试工作流. 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 workflow_execute: 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.
workflow_execute 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 workflow_execute 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 workflow_execute. 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.
workflow_execute 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.