This record as markdown: /tools/seac-25-kali-security-mcp/fuzz-all-params.md
What fuzz_all_params does on Kali Security MCP
AI agents invoke fuzz_all_params 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.
Why fuzz_all_params is rated High
This tool performs automated fuzzing across all parameters of a target, which actively sends crafted/malicious inputs to external systems. It executes attack-like probes against targets, constituting active exploitation activity.
From the tool's definition '全参数模糊测试 - 自动识别并测试所有参数' (full parameter fuzzing - automatically identify and test all parameters); part of a penetration testing server integrating 193 Kali Linux security tools
Attacks that exploit this kind of access
The rule that runs fuzz_all_params 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 fuzz_all_params, this is the rule to start with:
fuzz_all_params 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Kali Security MCP, apply this rule, and every fuzz_all_params call is checked against it from then on.
Questions about fuzz_all_params
全参数模糊测试 - 自动识别并测试所有参数. 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 fuzz_all_params: 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.
fuzz_all_params 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 fuzz_all_params 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 fuzz_all_params. 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.
fuzz_all_params 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.
Across the catalogue