openrouter-list
List configured OpenRouter delegates and settings. Pass mode (
This record as markdown: /tools/deliberation/openrouter-list.md
What openrouter-list does on Deliberation
AI agents call openrouter-list to retrieve information from Deliberation without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why openrouter-list is rated Low
This tool retrieves configuration information about OpenRouter delegates without modifying, executing, or deleting any data. It is a straightforward read operation with minimal blast radius if misused by an AI agent—the worst outcome would be information disclosure of non-sensitive configuration details.
From the tool's definition Tool name 'openrouter-list' and description 'List configured OpenRouter delegates and settings' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs openrouter-list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deliberation, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openrouter-list, this is the rule to start with:
openrouter-list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Deliberation, apply this rule, and every openrouter-list call is checked against it from then on.
Questions about openrouter-list
List configured OpenRouter delegates and settings. Pass mode (. It is categorised as a Read tool in the Deliberation MCP Server, which means it retrieves data without modifying state.
Register the Deliberation MCP server in PolicyLayer and add a rule for openrouter-list: 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 Deliberation. Nothing to install.
openrouter-list 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 openrouter-list 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 openrouter-list. 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.
openrouter-list is provided by the Deliberation MCP server (antonbabenko/deliberation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deliberation, and thousands of servers like it.
This server
Across the catalogue