# grok

Start a new Grok (xAI) expert session. Advisory only (no filesystem editing). Supports attaching files.

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

## Facts

- Tool: `grok`
- 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": "grok",
    "arguments": {}
  }
}
```

## Why grok is rated High

While labeled 'Advisory only (no filesystem editing)', initiating a session with an external LLM service and attaching files to that session triggers external processing. This is an Execute-category action because it runs a remote operation (Grok inference) whose outputs and side effects (API calls, quota consumption, potential information disclosure from attached files) depend on the provided arguments.

From the tool's own definition: "Tool description states 'Start a new Grok (xAI) expert session' and 'Supports attaching files'. The ability to initiate external API calls to Grok (xAI's language model) and attach arbitrary files constitutes execution of an external operation whose effects…"

## Use case

AI agents invoke grok 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": {
    "grok": {
      "limits": [
        {
          "counter": "grok_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-reply` — Execute — https://policylayer.com/tools/deliberation/grok-reply.md
- `openrouter` — Execute — https://policylayer.com/tools/deliberation/openrouter.md
- `openrouter-reply` — Execute — https://policylayer.com/tools/deliberation/openrouter-reply.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