Return scope-map entries, optionally filtered by resource name (bounded by default).
AI agents call get_scope_maps to retrieve information from API-Central without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Attacks that exploit this kind of access
Return scope-map entries, optionally filtered by resource name (bounded by default). It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.
Register the API-Central MCP server in PolicyLayer and add a rule for get_scope_maps: 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 API-Central. Nothing to install.
get_scope_maps 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_scope_maps 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_scope_maps. 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_scope_maps is provided by the API-Central MCP server (secure-ssid/centralmcp). 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 →