Get the status of a running scan
AI agents call get_scan_status to retrieve information from ZAP MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the status of an existing scan process. It retrieves information (scan progress, completion state, etc.) with no side effects, no data modification, and no capability to execute, delete, or initiate new operations. It is purely informational, consistent with the Read category for data retrieval operations.
From the tool's definition Tool name 'get_scan_status' and description 'Get the status of a running scan' indicate a read-only operation that retrieves current scan state without modifying data or triggering actions.
Attacks that exploit this kind of access
Get the status of a running scan. It is categorised as a Read tool in the ZAP MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ZAP MCP Server MCP server in PolicyLayer and add a rule for get_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 ZAP MCP Server. Nothing to install.
get_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 get_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 get_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.
get_scan_status is provided by the ZAP MCP Server MCP server (lisberndt/zap-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →