High Risk →

api_kiterunner_scan

Scan API endpoints using Kiterunner for route discovery.

How to control api_kiterunner_scan ↓

AI agents invoke api_kiterunner_scan to trigger actions in Zebbern Kali 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.

High Risk

This tool executes an active network scan against API endpoints using the Kiterunner penetration testing tool. It initiates outbound network connections and performs route discovery against target systems, which constitutes execution of an external operation. Within a Kali Linux pentest toolkit context alongside tools like secretsdump, psexec, and bloodhound, this is clearly an offensive reconnaissance tool.

From the tool's definition 'Scan API endpoints using Kiterunner for route discovery' — actively runs the Kiterunner tool against target API endpoints to discover routes

Documented attack patterns abuse exactly the kind of access api_kiterunner_scan gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Zebbern Kali MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for api_kiterunner_scan:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "api_kiterunner_scan": {
      "limits": [
        {
          "counter": "api_kiterunner_scan_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

api_kiterunner_scan 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.

  1. Create a free account and register Zebbern Kali MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the api_kiterunner_scan tool do? +

Scan API endpoints using Kiterunner for route discovery. It is categorised as a Execute tool in the Zebbern Kali MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on api_kiterunner_scan? +

Register the Zebbern Kali MCP server in PolicyLayer and add a rule for api_kiterunner_scan: 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 Zebbern Kali MCP. Nothing to install.

What risk level is api_kiterunner_scan? +

api_kiterunner_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit api_kiterunner_scan? +

Yes. Add a rate_limit block to the api_kiterunner_scan 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.

How do I block api_kiterunner_scan completely? +

Set action: deny in the PolicyLayer policy for api_kiterunner_scan. 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.

What MCP server provides api_kiterunner_scan? +

api_kiterunner_scan is provided by the Zebbern Kali MCP server (zebbern/zebbern-kali-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Zebbern Kali MCP tool call.

Deterministic rules across all 128 Zebbern Kali MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

128 Zebbern Kali MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.