Low Risk

list-data-centers

list-data-centers

How to control list-data-centers ↓

AI agents call list-data-centers to retrieve information from RunPod MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

The 'list' prefix and the absence of any create/delete/modify language indicate this tool retrieves or enumerates data centers available on RunPod without modifying state. While the description is empty, the name and context provide sufficient confidence that this is a read-only query operation.

From the tool's definition Tool name is 'list-data-centers' with 'list' indicating a retrieval operation. The sibling tools on the server (create-*, delete-*, cancel-*) suggest this is a management API; 'list-data-centers' follows the pattern of data retrieval with no side effects.

Documented attack patterns abuse exactly the kind of access list-data-centers gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and RunPod MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list-data-centers:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list-data-centers": {}
  }
}

list-data-centers is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register RunPod MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the list-data-centers tool do? +

list-data-centers. It is categorised as a Read tool in the RunPod MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list-data-centers? +

Register the RunPod MCP Server MCP server in PolicyLayer and add a rule for list-data-centers: 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 RunPod MCP Server. Nothing to install.

What risk level is list-data-centers? +

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

Can I rate-limit list-data-centers? +

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

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

list-data-centers is provided by the RunPod MCP Server MCP server (runpod/runpod-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every RunPod MCP Server tool call.

Deterministic rules across all 36 RunPod MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

36 RunPod MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.