AI agents call get_workflow_status to retrieve information from Kali Security MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the status of existing workflows. It performs a read operation with no side effects—it neither modifies data, executes commands, deletes resources, nor commits financial transactions. Despite being on a penetration testing platform, the tool itself is purely informational and cannot cause harm through misuse. Severity is low because retrieving status information has minimal blast radius.
From the tool's definition Tool name 'get_workflow_status' and description '获取工作流状态' (Get workflow status) indicate a retrieval/query operation that retrieves the current state of a workflow without modifying, executing, or destroying data.
Documented attack patterns abuse exactly the kind of access get_workflow_status 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 get_workflow_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_workflow_status": {}
}
}get_workflow_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
获取工作流状态。. It is categorised as a Read tool in the Kali Security MCP MCP Server, which means it retrieves data without modifying state.
Register the Kali Security MCP server in PolicyLayer and add a rule for get_workflow_status: 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.
get_workflow_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_workflow_status 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 get_workflow_status. 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.
get_workflow_status 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.