list_glp_tag_resources

List tagged workspace resources with bounded pagination.

SERVERHpe Networking SOURCEsecure-ssid/hpe-networking-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hpe-networking-mcp/list-glp-tag-resources.md

WHAT IT DOES

What list_glp_tag_resources does on Hpe Networking

AI agents call list_glp_tag_resources 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.

RISK

Why list_glp_tag_resources is rated Low

This tool queries and returns information about GreenLake Platform (GLP) tagged resources. The 'list' operation is non-destructive and has no side effects. Even if an AI agent misuses this tool, it can only retrieve existing data, not modify, delete, or execute operations. Pagination bounds prevent excessive data retrieval. Low severity due to minimal blast radius.

From the tool's definition Tool name 'list_glp_tag_resources' uses verb 'list' and description states 'List tagged workspace resources with bounded pagination' — classic read operation that retrieves data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_glp_tag_resources 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_glp_tag_resources, this is the rule to start with:

list_glp_tag_resources Allowed

list_glp_tag_resources is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hpe Networking, apply this rule, and every list_glp_tag_resources call is checked against it from then on.

FAQ

Questions about list_glp_tag_resources

What does the list_glp_tag_resources tool do? +

List tagged workspace resources with bounded pagination. It is categorised as a Read tool in the Hpe Networking MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_glp_tag_resources? +

Register the Hpe Networking MCP server in PolicyLayer and add a rule for list_glp_tag_resources: 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.

What risk level is list_glp_tag_resources? +

list_glp_tag_resources is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_glp_tag_resources? +

Yes. Add a rate_limit block to the list_glp_tag_resources 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 list_glp_tag_resources completely? +

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

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

KEEP EXPLORING

More on Hpe Networking, and thousands of servers like it.

This server

All 595 Hpe Networking tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →