list_scopes
A read tool on the Hpe Networking MCP server.
This record as markdown: /tools/hpe-networking-mcp/list-scopes.md
What list_scopes does on Hpe Networking
AI agents call list_scopes 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 list_scopes is rated Low
The tool appears to retrieve or enumerate scopes without modifying, deleting, or executing external operations. In the context of a research engine, 'list_scopes' most naturally performs a query returning available scopes. No evidence suggests data mutation, code execution, or destructive action. Confidence is slightly reduced due to empty description, but the naming pattern strongly indicates Read category.
From the tool's definition Tool name 'list_scopes' indicates a listing/retrieval operation. No description provided, but 'list' is a read-only query pattern consistent with other sibling tools like 'list_claims' and 'get_*' accessors.
Attacks that exploit this kind of access
The rule that runs list_scopes 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 list_scopes, this is the rule to start with:
list_scopes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hpe Networking, apply this rule, and every list_scopes call is checked against it from then on.
Questions about list_scopes
list_scopes is a read tool on the Hpe Networking MCP server. It is categorised as a Read tool in the Hpe Networking MCP Server, which means it retrieves data without modifying state.
Register the Hpe Networking MCP server in PolicyLayer and add a rule for list_scopes: 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 Hpe Networking. Nothing to install.
list_scopes 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 list_scopes 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 list_scopes. 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.
list_scopes is provided by the Hpe Networking MCP server (secure-ssid/hpe-networking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hpe Networking, and thousands of servers like it.
This server
Across the catalogue