AI agents call list_availability 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 appears to check availability of GPU resources—a read-only query with no side effects. While the description is empty (lowering confidence slightly), the naming convention and sibling tools on this server strongly suggest it retrieves availability information without modification or execution. The worst-case misuse would be resource enumeration, a low-severity concern.
From the tool's definition Tool name 'list_availability' indicates a query/listing operation. The server context shows this is part of a GPU pod management system alongside 'list_gpu_types' and 'pod_list', which are clearly Read operations.
Documented attack patterns abuse exactly the kind of access list_availability 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 list_availability:
{
"version": "1",
"default": "deny",
"tools": {
"list_availability": {}
}
}list_availability 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_availability. 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 list_availability: 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.
list_availability 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_availability 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_availability. 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_availability 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.