get_glp_location

Fetch one workspace location by ID.

SERVERAPI-Central SOURCEsecure-ssid/centralmcp

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/secure-ssid-centralmcp/get-glp-location.md

WHAT IT DOES

What get_glp_location does on API-Central

AI agents call get_glp_location to retrieve information from API-Central 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_location is rated Low

This tool retrieves data about a single GreenLake Platform workspace location by its identifier. 'Fetch' explicitly denotes a read-only operation. There is no indication of data modification, deletion, execution of commands, or financial impact.

From the tool's definition Tool name 'get_glp_location' and description 'Fetch one workspace location by ID' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_glp_location safely

PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_glp_location, this is the rule to start with:

get_glp_location Allowed

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

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

The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every get_glp_location call is checked against it from then on.

FAQ

Questions about get_glp_location

What does the get_glp_location tool do? +

Fetch one workspace location by ID. It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_glp_location? +

Register the API-Central MCP server in PolicyLayer and add a rule for get_glp_location: 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.

What risk level is get_glp_location? +

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

Can I rate-limit get_glp_location? +

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

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

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

KEEP EXPLORING

More on API-Central, and thousands of servers like it.

This server

All 590 API-Central 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 →