network_zero_trust_assess
AI agents invoke network_zero_trust_assess to trigger actions in Network Scanner MCP. 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.
The description is empty, so classification relies on the tool name and server context. 'Zero trust assess' implies active assessment/scanning of network infrastructure, which constitutes executing network operations (probing, fingerprinting, evaluating access controls) rather than a simple passive read.
From the tool's definition Tool name 'network_zero_trust_assess' on a server described as enabling 'network discovery, port scanning, and infrastructure monitoring' with 'service fingerprinting' for 'autonomous AI systems'.
Attacks that exploit this kind of access
network_zero_trust_assess. It is categorised as a Execute tool in the Network Scanner MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Network Scanner MCP server in PolicyLayer and add a rule for network_zero_trust_assess: 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_zero_trust_assess 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 network_zero_trust_assess 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_zero_trust_assess. 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_zero_trust_assess 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 →