list_glp_data_services_storage_locations
List Data Services storage locations (no server-side pagination per the manifest).
This record as markdown: /tools/secure-ssid-centralmcp/list-glp-data-services-storage-locations.md
What list_glp_data_services_storage_locations does on API-Central
AI agents call list_glp_data_services_storage_locations 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.
Why list_glp_data_services_storage_locations is rated Low
This tool queries and retrieves a list of storage locations without any side effects. It is purely informational and does not create, modify, delete, or execute any operations. The absence of server-side pagination is a technical implementation detail that does not elevate the risk category. Minimal blast radius if misused by an agent, as it only exposes read access to storage location metadata.
From the tool's definition Tool name contains 'list' and description states 'List Data Services storage locations' — a retrieval operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs list_glp_data_services_storage_locations 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 list_glp_data_services_storage_locations, this is the rule to start with:
list_glp_data_services_storage_locations 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 API-Central, apply this rule, and every list_glp_data_services_storage_locations call is checked against it from then on.
Questions about list_glp_data_services_storage_locations
List Data Services storage locations (no server-side pagination per the manifest). It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.
Register the API-Central MCP server in PolicyLayer and add a rule for list_glp_data_services_storage_locations: 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.
list_glp_data_services_storage_locations 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_glp_data_services_storage_locations 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_glp_data_services_storage_locations. 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_glp_data_services_storage_locations 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.
More on API-Central, and thousands of servers like it.
This server
Across the catalogue