AI agents invoke zap.start_active_scan to trigger actions in VulneraMCP. 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.
An active scan in OWASP ZAP sends malicious/probe payloads to a target application, constituting active exploitation attempts. This triggers external operations against target systems. The description is empty, but the tool name and server context (OWASP ZAP integration for vulnerability testing) strongly indicate this launches an active security scan.
From the tool's definition Tool name 'zap.start_active_scan' references OWASP ZAP active scanning, which actively probes and attacks target systems to find vulnerabilities.
Documented attack patterns abuse exactly the kind of access zap.start_active_scan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VulneraMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for zap.start_active_scan:
{
"version": "1",
"default": "deny",
"tools": {
"zap.start_active_scan": {
"limits": [
{
"counter": "zap.start_active_scan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}zap.start_active_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.
Free to start. No card required.
zap.start_active_scan. It is categorised as a Execute tool in the VulneraMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Vulnera MCP server in PolicyLayer and add a rule for zap.start_active_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 VulneraMCP. Nothing to install.
zap.start_active_scan 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 zap.start_active_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.
Set action: deny in the PolicyLayer policy for zap.start_active_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.
zap.start_active_scan is provided by the Vulnera MCP server (telmon95/vulneramcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 47 VulneraMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
47 VulneraMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.