7 tools. 1 can modify or destroy data without limits.
1 write tool that can modify data. Rate limits recommended.
Last updated:
Write operations (rigshare_create_booking) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
rigshare_create_booking:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
rigshare_get_equipment:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The Rigshare server has 1 write tools including rigshare_create_booking. 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.
7 tools across 2 categories: Read, Write. 6 are read-only. 1 can modify, create, or delete data.
One line change. Instead of running the Rigshare server directly, prefix it with Intercept: intercept -c io-github-rper2001-rigshare.yaml -- npx -y @rigshare-mcp. Download a pre-built policy from policylayer.com/policies/io-github-rper2001-rigshare and adjust the limits to match your use case.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.