4 tools. 2 can modify or destroy data without limits.
2 write tools that can modify data. Rate limits recommended.
Last updated:
Write operations (create_omi_conversation, create_omi_memories) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
create_omi_conversation:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
read_omi_conversations:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The Omi MCP Server server has 2 write tools including create_omi_conversation, create_omi_memories. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.
4 tools across 2 categories: Read, Write. 2 are read-only. 2 can modify, create, or delete data.
One line change. Instead of running the Omi MCP Server server directly, prefix it with Intercept: intercept -c fourcolors-omi-mcp.yaml -- npx -y @fourcolors/omi-mcp. Download a pre-built policy from policylayer.com/policies/fourcolors-omi-mcp and adjust the limits to match your use case.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.