Unsubscribe from a publisher's data feed. Takes effect next block: no more billing, no more data flow. Reversible — you can resubscribe later via byte_subscribe. Use this when a publisher has pivoted content (check with byte_subscription_health first) or when you simply don't want the feed anymor...
Part of the Byte MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call byte_unsubscribe to retrieve information from Byte without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though byte_unsubscribe only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
byte_unsubscribe:
rules:
- action: allowSee the full Byte policy for all 13 tools.
Agents calling read-class tools like byte_unsubscribe have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Unsubscribe from a publisher's data feed. Takes effect next block: no more billing, no more data flow. Reversible — you can resubscribe later via byte_subscribe. Use this when a publisher has pivoted content (check with byte_subscription_health first) or when you simply don't want the feed anymore. Requires PRIVATE_KEY for the connected wallet.. It is categorised as a Read tool in the Byte MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for byte_unsubscribe. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Byte MCP server.
byte_unsubscribe is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the byte_unsubscribe rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the Intercept policy for byte_unsubscribe. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
byte_unsubscribe is provided by the Byte MCP server (byte-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.