This record as markdown: /tools/seac-25-kali-security-mcp/workflow-define.md
What workflow_define does on Kali Security MCP
AI agents use workflow_define to create or update resources in Kali Security MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kali Security MCP environment.
Why workflow_define is rated Medium
The tool appears to define/create a workflow for testing purposes. 'Define' implies creating or configuring a workflow object (Write), rather than executing it. However, given the broader server context of penetration testing and the presence of sibling tools like 'adaptive_execute_strategy' and 'adaptive_intelligent_orchestration', this workflow definition could serve as a precursor to offensive operations.
From the tool's definition 工具名称 'workflow_define' 和描述 '定义测试工作流' (Define test workflow)
Attacks that exploit this kind of access
The rule that runs workflow_define 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 workflow_define, this is the rule to start with:
workflow_define stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 workflow_define call is checked against it from then on.
Questions about workflow_define
定义测试工作流. It is categorised as a Write tool in the Kali Security MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kali Security MCP server in PolicyLayer and add a rule for workflow_define: 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_define is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the workflow_define 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_define. 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_define 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.
This server
Across the catalogue