New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

market_get_history

Get price history for a coin (for charting).

SERVERBitcoin wallet MCP server SOURCEmarkmhendrickson/mcp-server-bitcoin
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/markmhendrickson-mcp-server-bitcoin/market-get-history.md

What market_get_history does on Bitcoin wallet MCP server

AI agents call market_get_history to retrieve information from Bitcoin wallet MCP server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why market_get_history is rated Low

This tool retrieves historical market data for informational/charting purposes. It performs a query operation that does not modify state, execute code, move funds, or delete data. The read-only nature and lack of side effects classify it as a Read operation with low severity—misuse would only expose price information already available publicly.

From the tool's definition Tool name 'market_get_history' and description 'Get price history for a coin (for charting)' indicate retrieval of historical price data with no modification or side effects.

Questions about market_get_history

What does the market_get_history tool do? +

Get price history for a coin (for charting). It is categorised as a Read tool in the Bitcoin wallet MCP server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on market_get_history? +

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

What risk level is market_get_history? +

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

Can I rate-limit market_get_history? +

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

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

market_get_history is provided by the Bitcoin wallet MCP server MCP server (markmhendrickson/mcp-server-bitcoin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Bitcoin wallet MCP server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Bitcoin wallet MCP server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.