AI agents call zap.get_active_scan_status to retrieve information from VulneraMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the status of an active security scan from OWASP ZAP without performing any side effects, modifications, deletions, or executing new operations. It queries existing state information. While the description is empty (reducing confidence slightly), the clear naming convention and context among security scanning tools indicate this is a status query operation.
From the tool's definition Tool name 'get_active_scan_status' indicates retrieval of scan status information with no modification capability. The 'get_' prefix strongly suggests a read operation.
Documented attack patterns abuse exactly the kind of access zap.get_active_scan_status 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.get_active_scan_status:
{
"version": "1",
"default": "deny",
"tools": {
"zap.get_active_scan_status": {}
}
}zap.get_active_scan_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
zap.get_active_scan_status. It is categorised as a Read tool in the VulneraMCP MCP Server, which means it retrieves data without modifying state.
Register the Vulnera MCP server in PolicyLayer and add a rule for zap.get_active_scan_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 VulneraMCP. Nothing to install.
zap.get_active_scan_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the zap.get_active_scan_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.
Set action: deny in the PolicyLayer policy for zap.get_active_scan_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.
zap.get_active_scan_status 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.