list-templates
AI agents call list-templates 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.
The tool retrieves or queries template data from the RunPod API without modifying, deleting, or executing operations. Even though the description is empty, the naming convention 'list-' is unambiguous—it retrieves information. The severity is low because listing templates poses minimal risk; an AI agent reading template metadata cannot cause harm unless it subsequently uses another tool to create or delete resources.
From the tool's definition Tool name 'list-templates' indicates a listing/querying operation with no side effects. The 'list-' prefix is a standard convention for retrieval operations. No description provided, but the name strongly suggests data retrieval.
Attacks that exploit this kind of access
list-templates. It is categorised as a Read tool in the RunPod MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RunPod MCP Server MCP server in PolicyLayer and add a rule for list-templates: 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.
list-templates 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-templates 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-templates. 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-templates is provided by the RunPod MCP Server MCP server (niel-runpod/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →