This record as markdown: /tools/seac-25-kali-security-mcp/http-send-raw.md
What http_send_raw does on Kali Security MCP
AI agents invoke http_send_raw 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 http_send_raw is rated High
This tool sends arbitrary raw HTTP requests with full format control, meaning it can trigger external operations, interact with web services, exploit vulnerabilities, or perform reconnaissance. In the context of a penetration testing server with tools like adaptive_cmdi_test and adaptive_sqli_test, this tool is clearly designed for offensive security operations.
From the tool's definition 发送原始HTTP请求 - 完全控制请求格式 (Send raw HTTP requests - full control over request format)
Attacks that exploit this kind of access
The rule that runs http_send_raw 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 http_send_raw, this is the rule to start with:
http_send_raw 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 http_send_raw call is checked against it from then on.
Questions about http_send_raw
发送原始HTTP请求 - 完全控制请求格式. 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 http_send_raw: 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.
http_send_raw 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 http_send_raw 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 http_send_raw. 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.
http_send_raw 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