AI agents call zap.health_check 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.
Health checks are passive operations that query the status of a service (OWASP ZAP in this case) and return diagnostic information without side effects. This is a read operation with minimal blast radius—even if invoked inappropriately, it only returns status information. Confidence is reduced slightly due to empty description, but the naming convention strongly indicates a benign diagnostic function.
From the tool's definition Tool name 'health_check' indicates a diagnostic query operation that checks service status without modifying data or triggering external actions. No description provided, but health checks are standard read-only operations.
Documented attack patterns abuse exactly the kind of access zap.health_check 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.health_check:
{
"version": "1",
"default": "deny",
"tools": {
"zap.health_check": {}
}
}zap.health_check 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.health_check. 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.health_check: 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.health_check 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.health_check 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.health_check. 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.health_check 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.