network_defense
Network: connections, traffic capture, port scan detection, IPv6 audit, self-scan, segmentation
This record as markdown: /tools/defense/network-defense.md
What network_defense does on Defense
AI agents use network_defense to create or update resources in Defense, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Defense environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
count | number | — | Number of packets to capture |
action | string | Yes | Network defense action |
filter | string | — | BPF filter expression |
target | string | — | Scan target |
dry_run | boolean | — | Preview without executing |
process | boolean | — | Show process information |
duration | number | — | Capture duration in seconds |
log_file | string | — | Log file to analyze |
protocol | string | — | Protocol filter |
dest_zone | string | — | Destination network zone/subnet CIDR |
interface | string | — | Network interface to capture on |
listening | boolean | — | Show only listening sockets |
Parameters from the server's own tool schema.
Why network_defense is rated Medium
An AI agent can call network_defense faster than any human can review: one bad instruction and it creates or modifies resources in Defense by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (19 properties)
Attacks that exploit this kind of access
The rule that runs network_defense 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 network_defense, this is the rule to start with:
network_defense stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 network_defense call is checked against it from then on.
Questions about network_defense
Network: connections, traffic capture, port scan detection, IPv6 audit, self-scan, segmentation. It is categorised as a Write tool in the Defense MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
network_defense accepts 12 parameters: count, action, filter, target, dry_run, process, duration, log_file, protocol, dest_zone, interface, listening. 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 network_defense: 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.
network_defense is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the network_defense 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 network_defense. 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.
network_defense 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.
This server
Across the catalogue