Low Risk

vpn_status

vpn_status

How to control vpn_status ↓

AI agents call vpn_status to retrieve information from Zebbern Kali MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

The tool name 'vpn_status' strongly suggests a read-only query operation to check VPN connectivity or configuration state. This aligns with the 'Read' category (retrieves or queries data with no side effects). The empty description reduces confidence slightly, but the naming convention is clear. Status checks are non-destructive, non-modifying operations.

From the tool's definition Tool name 'vpn_status' implies querying VPN connection state or configuration. The description is empty, limiting certainty.

Documented attack patterns abuse exactly the kind of access vpn_status 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 vpn_status:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "vpn_status": {}
  }
}

vpn_status is read-only, so it stays allowed — but 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.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the vpn_status tool do? +

vpn_status. It is categorised as a Read tool in the Zebbern Kali MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on vpn_status? +

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

What risk level is vpn_status? +

vpn_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit vpn_status? +

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

How do I block vpn_status completely? +

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

What MCP server provides vpn_status? +

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