Low Risk

tf_premium_exchange_flows

Tracks ETH transfers in/out of major centralized exchange hot wallets (Binance, Coinbase, OKX, Kraken, Bybit, Crypto.com, KuCoin) in the last 3 blocks. Each transfer tagged as inflow (user -> exchange, often precedes selling), outflow (exchange -> user, often HODL withdrawal), or inter_exchange. ...

Part of the Terminalfeed server.

tf_premium_exchange_flows is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE TERMINALFEED →

Free to start. No card required.

AI agents call tf_premium_exchange_flows to retrieve information from Terminalfeed 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 tf_premium_exchange_flows 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "tf_premium_exchange_flows": {}
  }
}

See the full Terminalfeed policy for all 35 tools.

Get this rule live on your own Terminalfeed server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY TERMINALFEED →

View all 35 tools →

These attack patterns abuse exactly the kind of access tf_premium_exchange_flows gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so tf_premium_exchange_flows only ever does what you allow.

SECURE TERMINALFEED →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the tf_premium_exchange_flows tool do? +

Tracks ETH transfers in/out of major centralized exchange hot wallets (Binance, Coinbase, OKX, Kraken, Bybit, Crypto.com, KuCoin) in the last 3 blocks. Each transfer tagged as inflow (user -> exchange, often precedes selling), outflow (exchange -> user, often HODL withdrawal), or inter_exchange. Aggregated per-exchange and globally with net_eth, net_usd, and bias label (inflow_dominant / outflow_dominant / balanced). Threshold 5 ETH minimum (~$11K at $2300/ETH) to filter retail noise. Useful for trading bots detecting regime shifts: sustained large net inflow signals selling pressure ahead, sustained outflow signals accumulation. Pair with tf_premium_whales for context. Costs 2 credits ($0.04 USDC). 5-min cache. Bearer auth required. v1 covers ETH only; BTC requires a labeled-address dataset.. It is categorised as a Read tool in the Terminalfeed MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on tf_premium_exchange_flows? +

Register the Terminalfeed MCP server in PolicyLayer and add a rule for tf_premium_exchange_flows: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Terminalfeed. Nothing to install.

What risk level is tf_premium_exchange_flows? +

tf_premium_exchange_flows is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit tf_premium_exchange_flows? +

Yes. Add a rate_limit block to the tf_premium_exchange_flows rule in your PolicyLayer 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.

How do I block tf_premium_exchange_flows completely? +

Set action: deny in the PolicyLayer policy for tf_premium_exchange_flows. 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.

What MCP server provides tf_premium_exchange_flows? +

tf_premium_exchange_flows is provided by the Terminalfeed MCP server (https://terminalfeed.io/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Terminalfeed tool call.

Deterministic rules across all 35 Terminalfeed tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.