5 tools. 3 can modify or destroy data without limits.
3 write tools that can modify data. Rate limits recommended.
Last updated:
Write operations (`set_current_project`, `set_current_working_directory`) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Execute tools (`reauth`) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
`set_current_project`:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
`get_project_schema`:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The Momen server has 2 write tools including `set_current_project`, `set_current_working_directory`. 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.
5 tools across 3 categories: Execute, Read, Write. 2 are read-only. 3 can modify, create, or delete data.
One line change. Instead of running the Momen server directly, prefix it with Intercept: intercept -c momen.yaml -- npx -y @momen-mcp. Download a pre-built policy from policylayer.com/policies/momen and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.