Get current status of the network scanner.
AI agents call get_scanner_status to retrieve information from Network Scanner MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the current operational state of the scanner itself—a read-only operation with no side effects. It does not scan networks, modify configurations, execute code, or delete data. The low severity reflects minimal blast radius if misused by an AI agent; status information alone poses limited security risk.
From the tool's definition Tool name 'get_scanner_status' and description 'Get current status of the network scanner' indicate a query operation that retrieves status information without modifying, executing against external systems, or causing destructive changes.
Attacks that exploit this kind of access
Get current status of the network scanner. It is categorised as a Read tool in the Network Scanner MCP MCP Server, which means it retrieves data without modifying state.
Register the Network Scanner MCP server in PolicyLayer and add a rule for get_scanner_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 Network Scanner MCP. Nothing to install.
get_scanner_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_scanner_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_scanner_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_scanner_status is provided by the Network Scanner MCP server (marc-shade/network-scanner-mcp). 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 →