AI agents invoke submit_workflow 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 tools, penetration testing, automated workflows) and sibling tools (ad_full_attack, adaptive_network_penetration, adaptive_web_penetration, etc.), 'submit_workflow' almost certainly triggers execution of automated security/attack workflows. The empty description lowers confidence, but the context strongly implies Execute-level risk at minimum.
From the tool's definition Tool name 'submit_workflow' on a server described as integrating 193 Kali Linux security tools for penetration testing and automated workflows. Description is empty/uninformative.
Documented attack patterns abuse exactly the kind of access submit_workflow 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 submit_workflow:
{
"version": "1",
"default": "deny",
"tools": {
"submit_workflow": {
"limits": [
{
"counter": "submit_workflow_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}submit_workflow 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.
submit_workflow. 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 submit_workflow: 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.
submit_workflow 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 submit_workflow 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 submit_workflow. 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.
submit_workflow 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.