AI agents invoke zap.start_spider 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.
A ZAP spider initiates an active crawling operation against a target web application, which constitutes executing an external operation. The description is empty, lowering confidence, but the name strongly implies triggering OWASP ZAP's spider/crawler which sends many HTTP requests to external systems. This could constitute unauthorized scanning if misused, giving it high severity.
From the tool's definition Tool name 'zap.start_spider' combined with server context integrating OWASP ZAP for automated reconnaissance and vulnerability testing. Spider tools crawl/scan external targets.
Documented attack patterns abuse exactly the kind of access zap.start_spider 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_spider:
{
"version": "1",
"default": "deny",
"tools": {
"zap.start_spider": {
"limits": [
{
"counter": "zap.start_spider_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}zap.start_spider 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_spider. 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_spider: 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_spider 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_spider 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_spider. 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_spider 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.