List models available on OpenRouter.
AI agents call list_models to retrieve information from OpenRouter MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation to enumerate or retrieve metadata about AI models. It has no side effects, does not execute code, does not modify data, and does not involve financial transactions. The blast radius of misuse is minimal—an agent could only discover what models are available, which is informational and reversible. This is a classic 'Read' category tool.
From the tool's definition Tool name 'list_models' and description 'List models available on OpenRouter' indicate a query operation that retrieves information about available models without modifying any data or triggering external operations.
Attacks that exploit this kind of access
List models available on OpenRouter. It is categorised as a Read tool in the OpenRouter MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenRouter MCP Server MCP server in PolicyLayer and add a rule for 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 OpenRouter MCP Server. Nothing to install.
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 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 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.
list_models is provided by the OpenRouter MCP Server MCP server (lumishoang/openrouter-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 →