openrouter-reply
Continue an OpenRouter session by threadId (in-memory; lost on restart).
This record as markdown: /tools/deliberation/openrouter-reply.md
What openrouter-reply does on Deliberation
AI agents invoke openrouter-reply to trigger actions in Deliberation. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why openrouter-reply is rated High
Although the tool itself does not execute local code or shell commands, it executes prompts against external LLM models via the OpenRouter API. This is a form of execute because it triggers external operations with effects contingent on user input.
From the tool's definition The tool 'openrouter-reply' continues an OpenRouter session by threadId, which sends requests to external LLM APIs (400+ models including Qwen, Kimi, DeepSeek).
Attacks that exploit this kind of access
The rule that runs openrouter-reply 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-reply, this is the rule to start with:
openrouter-reply stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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-reply call is checked against it from then on.
Questions about openrouter-reply
Continue an OpenRouter session by threadId (in-memory; lost on restart). It is categorised as a Execute tool in the Deliberation MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Deliberation MCP server in PolicyLayer and add a rule for openrouter-reply: 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-reply is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the openrouter-reply 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-reply. 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-reply 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.
Across the catalogue