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