# openrouter-reply

Continue an OpenRouter session by threadId (in-memory; lost on restart).

Agent View of the PolicyLayer registry record for `openrouter-reply`. HTML page: https://policylayer.com/tools/deliberation/openrouter-reply

## Facts

- Tool: `openrouter-reply`
- Server: Deliberation (`antonbabenko/deliberation`) — https://policylayer.com/tools/deliberation.md
- Homepage: https://github.com/antonbabenko/deliberation
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "openrouter-reply",
    "arguments": {}
  }
}
```

## 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 own definition: "The tool 'openrouter-reply' continues an OpenRouter session by threadId, which sends requests to external LLM APIs (400+ models including Qwen, Kimi, DeepSeek)."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Deliberation:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "openrouter-reply": {
      "limits": [
        {
          "counter": "openrouter-reply_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Deliberation (10)

- `consensus` — Execute — https://policylayer.com/tools/deliberation/consensus.md
- `consensus-step` — Execute — https://policylayer.com/tools/deliberation/consensus-step.md
- `gemini` — Execute — https://policylayer.com/tools/deliberation/gemini.md
- `gemini-reply` — Execute — https://policylayer.com/tools/deliberation/gemini-reply.md
- `grok` — Execute — https://policylayer.com/tools/deliberation/grok.md
- `grok-reply` — Execute — https://policylayer.com/tools/deliberation/grok-reply.md
- `openrouter` — Execute — https://policylayer.com/tools/deliberation/openrouter.md
- `analyze` — Read — https://policylayer.com/tools/deliberation/analyze.md
- `openrouter-list` — Read — https://policylayer.com/tools/deliberation/openrouter-list.md
- `session-get` — Read — https://policylayer.com/tools/deliberation/session-get.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=deliberation · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/deliberation