Low Risk

get_tickers_jpy

全JPYペアのティッカーを取得(/tickers_jpy)。24h変動率付き。キャッシュ10秒。

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

AI agents call get_tickers_jpy 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_tickers_jpy 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_tickers_jpy:
    rules:
      - action: allow

See the full Bitbank policy for all 5 tools.

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

Agents calling read-class tools like get_tickers_jpy 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_tickers_jpy tool do? +

全JPYペアのティッカーを取得(/tickers_jpy)。24h変動率付き。キャッシュ10秒。. 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_tickers_jpy? +

Add a rule in your Intercept YAML policy under the tools section for get_tickers_jpy. 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_tickers_jpy? +

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

Can I rate-limit get_tickers_jpy? +

Yes. Add a rate_limit block to the get_tickers_jpy 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_tickers_jpy completely? +

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

get_tickers_jpy 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.