AI agents use pod_create to commit financial operations through Prime Intellect — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Creating a GPU pod on this platform directly incurs costs (rental charges), making this a Financial action. The server description explicitly mentions spend caps and autonomous provisioning of paid cloud resources. Misuse could rapidly exhaust funds, warranting critical severity.
From the tool's definition Tool name 'pod_create' on a server described as enabling agents to 'rent, drive, and terminate Prime Intellect GPU pods with hard spend caps' — creation of a GPU pod constitutes renting cloud resources and committing financial obligations.
Documented attack patterns abuse exactly the kind of access pod_create 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_create:
{
"version": "1",
"default": "deny",
"tools": {
"pod_create": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to pod_create is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
pod_create. It is categorised as a Financial tool in the Prime Intellect MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Prime Intellect MCP server in PolicyLayer and add a rule for pod_create: 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_create is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the pod_create 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_create. 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_create 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.