zero_trust
Zero-trust: WireGuard VPN, peer management, mTLS certificates, microsegmentation
This record as markdown: /tools/defense/zero-trust.md
What zero_trust does on Defense
AI agents invoke zero_trust to trigger actions in Defense. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
action | string | Yes | Zero-trust networking action |
dryRun | boolean | — | Preview only |
address | string | — | Interface address with CIDR e.g. 10.0.0.1/24 |
denyAll | boolean | — | Add deny-all rule for other ports |
service | string | — | Service name e.g. nginx, postgres |
clientCN | string | — | Client common name |
endpoint | string | — | Peer endpoint ip:port |
serverCN | string | — | Server common name |
outputDir | string | — | Directory to write certificates |
publicKey | string | — | Peer public key |
validDays | number | — | Certificate validity in days |
allowPorts | array | — | Ports to allow |
Parameters from the server's own tool schema.
Why zero_trust is rated High
The zero_trust tool configures network security infrastructure including VPN tunnels, peer management, mTLS certificate issuance, and microsegmentation policies. These operations actively modify network configurations, create/manage cryptographic certificates, and enforce access control boundaries.
From the tool's definition WireGuard VPN, peer management, mTLS certificates, microsegmentation
Risk signalsAccepts URL/endpoint input (endpoint) · High parameter count (18 properties)
Attacks that exploit this kind of access
The rule that runs zero_trust safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Defense, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zero_trust, this is the rule to start with:
zero_trust 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 Defense, apply this rule, and every zero_trust call is checked against it from then on.
Questions about zero_trust
Zero-trust: WireGuard VPN, peer management, mTLS certificates, microsegmentation. It is categorised as a Execute tool in the Defense MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
zero_trust accepts 12 parameters: action, dryRun, address, denyAll, service, clientCN, endpoint, serverCN, outputDir, publicKey, validDays, allowPorts. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the Defense MCP server in PolicyLayer and add a rule for zero_trust: 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 Defense. Nothing to install.
zero_trust 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 zero_trust 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 zero_trust. 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.
zero_trust is provided by the Defense MCP server (defense-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Defense, and thousands of servers like it.
Across the catalogue