List the live model catalog with capabilities and prices.${NO_AUTH}
AI agents call venice_list_models to retrieve information from Venice MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns data about available models and their pricing without modifying, creating, or deleting any data. It is a straightforward read operation similar to a catalog lookup or list endpoint. The ${NO_AUTH} notation suggests it may not require authentication, further indicating it is a safe informational query.
From the tool's definition Tool name is 'venice_list_models' and description states 'List the live model catalog with capabilities and prices.' This is a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access venice_list_models gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Venice MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for venice_list_models:
{
"version": "1",
"default": "deny",
"tools": {
"venice_list_models": {}
}
}venice_list_models 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 the live model catalog with capabilities and prices.${NO_AUTH}. It is categorised as a Read tool in the Venice MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Venice MCP Server MCP server in PolicyLayer and add a rule for venice_list_models: 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 Venice MCP Server. Nothing to install.
venice_list_models 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 venice_list_models 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 venice_list_models. 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.
venice_list_models is provided by the Venice MCP Server MCP server (veniceai/venice-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 27 Venice MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
27 Venice MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.