Low Risk

get_depth

板の生データ取得(/depth API直接)。差分計算・壁検出・圧力分析の元データ。maxLevelsで層数制限。

Part of the Bitbank MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

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

bitbank.yaml
tools:
  get_depth:
    rules:
      - action: allow

See the full Bitbank policy for all 5 tools.

Tool Name get_depth
Category Read
MCP Server Bitbank MCP Server
Risk Level Low

Agents calling read-class tools like get_depth have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the get_depth tool do? +

板の生データ取得(/depth API直接)。差分計算・壁検出・圧力分析の元データ。maxLevelsで層数制限。. It is categorised as a Read tool in the Bitbank MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_depth? +

Add a rule in your Intercept YAML policy under the tools section for get_depth. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Bitbank MCP server.

What risk level is get_depth? +

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

Can I rate-limit get_depth? +

Yes. Add a rate_limit block to the get_depth 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.

How do I block get_depth completely? +

Set action: deny in the Intercept policy for get_depth. 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 get_depth? +

get_depth is provided by the Bitbank MCP server (bitbank-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Bitbank

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.