AI agents invoke auto_osint_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.
This tool executes automated OSINT (Open Source Intelligence) workflows against targets, actively running intelligence gathering operations. It is part of a penetration testing server with tools like 'adaptive_network_penetration' and 'ad_full_attack', indicating it triggers real external reconnaissance operations. The phrase '实际执行' (actually executes) confirms active execution rather than passive retrieval.
From the tool's definition 自动化OSINT情报收集工作流 - 实际执行开源情报收集 (Automated OSINT intelligence gathering workflow - actually executes open source intelligence collection)
Documented attack patterns abuse exactly the kind of access auto_osint_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 auto_osint_workflow:
{
"version": "1",
"default": "deny",
"tools": {
"auto_osint_workflow": {
"limits": [
{
"counter": "auto_osint_workflow_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}auto_osint_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.
自动化OSINT情报收集工作流 - 实际执行开源情报收集。. 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 auto_osint_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.
auto_osint_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 auto_osint_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 auto_osint_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.
auto_osint_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.