get_scope_maps

What get_scope_maps does on Hpe Networking

AI agents call get_scope_maps to retrieve information from Hpe Networking without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_scope_maps is rated Low

This tool retrieves existing scope-map configuration entries from HPE Aruba Central without creating, modifying, deleting, or executing operations. Filtering and returning data are non-destructive read operations. The blast radius of misuse is low—an AI agent querying scope maps poses minimal risk compared to tools that modify network configuration or execute commands.

From the tool's definition Tool name 'get_scope_maps' and description 'Return scope-map entries, optionally filtered by resource name' indicate a retrieval/query operation with no side effects. The phrase 'return' and 'filtered by' are characteristic of read operations.

The rule that runs get_scope_maps safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hpe Networking, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_scope_maps, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_scope_maps": {}
  }
}

Questions about get_scope_maps