List every pod the API key can see (active + provisioning + stopped).
AI agents call pod_list to retrieve information from Prime Intellect without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns information about existing GPU pods without creating, modifying, deleting, or executing anything. It is a straightforward read operation. While the context involves cloud resource management with financial implications, this specific tool has no direct financial, destructive, or execution capabilities — it merely enumerates resources.
From the tool's definition Tool description states 'List every pod the API key can see (active + provisioning + stopped)' — a pure retrieval operation with no modification or resource consumption.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access pod_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Prime Intellect, and nothing reaches the server without passing your rules. This is the rule we recommend for pod_list:
{
"version": "1",
"default": "deny",
"tools": {
"pod_list": {}
}
}pod_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List every pod the API key can see (active + provisioning + stopped). It is categorised as a Read tool in the Prime Intellect MCP Server, which means it retrieves data without modifying state.
Register the Prime Intellect MCP server in PolicyLayer and add a rule for pod_list: 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 Prime Intellect. Nothing to install.
pod_list 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 pod_list 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 pod_list. 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.
pod_list is provided by the Prime Intellect MCP server (kvrancic/prime-intellect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Prime Intellect, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 Prime Intellect tools catalogued and risk-classified — across an index of 43,000+ MCP servers.