vuln_manage
Vulnerabilities: nmap scan, nikto web scan, tracking, risk prioritization, remediation plans
This record as markdown: /tools/defense/vuln-manage.md
What vuln_manage does on Defense
AI agents invoke vuln_manage 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 | Vulnerability management action |
status | string | — | Vulnerability status |
target | string | — | IP, hostname, or URL to scan |
vuln_id | string | — | Vulnerability ID for tracking |
severity | string | — | Severity level for new vulnerability |
scan_type | string | — | Scan type |
port_range | string | — | Port range for scanning |
description | string | — | Vulnerability description |
output_format | string | — | Output format |
severity_filter | string | — | Severity filter for prioritization |
Parameters from the server's own tool schema.
Why vuln_manage is rated High
This tool executes active scanning tools (nmap, nikto) against systems, which involves initiating network connections and probing targets. This is Execute category because it runs external operations whose effects depend on arguments. Severity is high because misconfigured scans could target unintended systems, cause service disruption, or expose sensitive network topology information.
From the tool's definition nmap scan, nikto web scan — actively runs network and web vulnerability scanners against targets
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs vuln_manage 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 vuln_manage, this is the rule to start with:
vuln_manage 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 vuln_manage call is checked against it from then on.
Questions about vuln_manage
Vulnerabilities: nmap scan, nikto web scan, tracking, risk prioritization, remediation plans. 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.
vuln_manage accepts 10 parameters: action, status, target, vuln_id, severity, scan_type, port_range, description, output_format, severity_filter. 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 vuln_manage: 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.
vuln_manage 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 vuln_manage 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 vuln_manage. 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.
vuln_manage 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