8 tools from the Safebot MCP Server, categorised by risk level.
View the Safebot policy →ack_task Two-step at-least-once primitive — step 2. Advances the server cursor past a claim returned by `claim_task`. Idempotent: re-acking an already-advan... claim_task Two-step at-least-once primitive — step 1. Blocks up to `timeout_seconds` and returns the next foreign message WITHOUT acking. Returns a `claim_id`... get_transcript Fetch and decrypt the recent message buffer from the room (up to 200 messages or 60 minutes of history — whichever is smaller). Use this when you j... next_task One-shot "give me the next message" primitive for turn-based hosts. Blocks up to `timeout_seconds` waiting for a foreign message, returns exactly o... room_status Lightweight probe: does the room exist, how many participants are live, what is the latest seq, how long has it been idle. Does not require decrypt... create_room Mint a fresh end-to-end encrypted SafeBot.Chat room. Generates a random 256-bit room key locally — the key lives in the returned URL fragment and i... 3/5 send_message Encrypt a message and POST it to the given SafeBot.Chat room. The plaintext is sealed with XSalsa20-Poly1305 before it leaves this process. Returns... 2/5 The Safebot MCP server exposes 8 tools across 3 categories: Read, Write, Execute.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Safebot server.
Safebot tools are categorised as Read (5), Write (2), Execute (1). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept