Low Risk

product_book

Coinbase Exchange (US-regulated crypto venue) live order book — bids + asks for a crypto pair like "BTC-USD". Levels 1-3 control depth. Use for spread analysis, liquidity assessment, market making.

Part of the Coinbase Exchange server.

product_book 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 COINBASE EXCHANGE →

Free to start. No card required.

AI agents call product_book to retrieve information from Coinbase Exchange 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 product_book 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": {
    "product_book": {}
  }
}

See the full Coinbase Exchange policy for all 30 tools.

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

ENFORCE ON MY COINBASE EXCHANGE →

View all 30 tools →

These attack patterns abuse exactly the kind of access product_book 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 product_book only ever does what you allow.

SECURE COINBASE EXCHANGE →

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

What does the product_book tool do? +

Coinbase Exchange (US-regulated crypto venue) live order book — bids + asks for a crypto pair like "BTC-USD". Levels 1-3 control depth. Use for spread analysis, liquidity assessment, market making.. It is categorised as a Read tool in the Coinbase Exchange MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on product_book? +

Register the Coinbase Exchange MCP server in PolicyLayer and add a rule for product_book: 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 Coinbase Exchange. Nothing to install.

What risk level is product_book? +

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

Can I rate-limit product_book? +

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

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

product_book is provided by the Coinbase Exchange MCP server (https://gateway.pipeworx.io/coinbase-exchange/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Coinbase Exchange tool call.

Deterministic rules across all 30 Coinbase Exchange 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.