get_glp_workspace

Fetch basic GreenLake workspace information by workspace ID.

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/get-glp-workspace.md

WHAT IT DOES

What get_glp_workspace does on Hpe Networking

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

The tool fetches (retrieves) workspace information without modifying, deleting, or executing operations. The verb 'Fetch' and lack of any modification capability places this firmly in the Read category. Severity is low because workspace metadata retrieval has minimal blast radius even if misused by an AI agent.

From the tool's definition Tool name 'get_glp_workspace' and description 'Fetch basic GreenLake workspace information by workspace ID' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_glp_workspace Allowed

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

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

FAQ

Questions about get_glp_workspace

What does the get_glp_workspace tool do? +

Fetch basic GreenLake workspace information by workspace ID. 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 get_glp_workspace? +

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

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

Can I rate-limit get_glp_workspace? +

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

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

get_glp_workspace 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_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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