export_for_security_scan · Network Scanner MCP

WHAT IT DOES

What export_for_security_scan does on Network Scanner MCP

AI agents use export_for_security_scan to create or update resources in Network Scanner MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Network Scanner MCP environment.

WHY IT NEEDS A POLICY

Why export_for_security_scan needs a policy

The tool creates or exports data (devices list) into a format suitable for external security scanners. While it doesn't modify the original data irreversibly (making it not Destructive), and doesn't execute arbitrary code (making it not Execute), it does write/prepare data for external consumption.

From the tool's definition Tool name 'export_for_security_scan' and description 'Export discovered devices for security scanning integration' indicate data preparation and export functionality.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

export_for_security_scan Rate-limited

export_for_security_scan stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_for_security_scan": {
      "limits": [
        {
          "counter": "export_for_security_scan_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Network Scanner MCP, so you can run agents against it safely.

FAQ

Questions about export_for_security_scan

What does the export_for_security_scan tool do? +

Export discovered devices for security scanning integration. It is categorised as a Write tool in the Network Scanner MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on export_for_security_scan? +

Register the Network Scanner MCP server in PolicyLayer and add a rule for export_for_security_scan: 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.

What risk level is export_for_security_scan? +

export_for_security_scan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit export_for_security_scan? +

Yes. Add a rate_limit block to the export_for_security_scan 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.

How do I block export_for_security_scan completely? +

Set action: deny in the PolicyLayer policy for export_for_security_scan. 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.

What MCP server provides export_for_security_scan? +

export_for_security_scan 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.