network_compliance_map
AI agents call network_compliance_map 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.
The tool name suggests mapping or querying network compliance data rather than modifying, deleting, or executing operations. Given the broader server context of monitoring and discovery (detect_new_devices, discover_services, get_device_info), this aligns with Read category. However, absent a clear description, confidence is moderate.
From the tool's definition Tool name 'network_compliance_map' and sibling tools (get_network_topology, get_device_info, get_cluster_nodes) indicate data retrieval operations. Description is empty, limiting certainty.
Attacks that exploit this kind of access
network_compliance_map. 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 network_compliance_map: 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.
network_compliance_map 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 network_compliance_map 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 network_compliance_map. 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.
network_compliance_map 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 →