list_static_tags

List user-created static classification tags (bounded). System tags (e.g. IoT) not returned.

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-static-tags.md

WHAT IT DOES

What list_static_tags does on Hpe Networking

AI agents call list_static_tags 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_static_tags is rated Low

This tool queries and returns existing static tags without creating, modifying, deleting, or executing any actions. It is bounded retrieval of metadata about network device classification tags. The low severity reflects minimal blast radius—an AI agent misusing this to list tags poses no risk of data loss, unauthorized changes, or unintended operations.

From the tool's definition Tool name 'list_static_tags' and description 'List user-created static classification tags' indicate a retrieval operation with no side effects. The verb 'list' is explicitly a Read operation per the classification rules.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_static_tags Allowed

list_static_tags 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_static_tags": {}
  }
}

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_static_tags call is checked against it from then on.

FAQ

Questions about list_static_tags

What does the list_static_tags tool do? +

List user-created static classification tags (bounded). System tags (e.g. IoT) not returned. 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_static_tags? +

Register the Hpe Networking MCP server in PolicyLayer and add a rule for list_static_tags: 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_static_tags? +

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

Can I rate-limit list_static_tags? +

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

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

list_static_tags 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

get_cocktail_by_tags on Cocktails RAG MCP Server →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 →