stx_read_contract

Read-only call to a Clarity contract function (no transaction needed).

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/stx-read-contract.md

WHAT IT DOES

What stx_read_contract does on Bitcoin wallet MCP server

AI agents call stx_read_contract 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.

RISK

Why stx_read_contract is rated Low

This tool queries contract state via a read-only operation, which is a safe, non-destructive action with no financial or operational side effects. Even in a financial/cryptocurrency context, read-only contract calls pose minimal risk as they cannot modify state, execute transactions, or move funds. Low severity is appropriate for pure information retrieval.

From the tool's definition Tool name explicitly contains 'read' and description states 'Read-only call' with 'no transaction needed', indicating retrieval of contract state without side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs stx_read_contract safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Bitcoin wallet MCP server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stx_read_contract, this is the rule to start with:

stx_read_contract Allowed

stx_read_contract is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stx_read_contract": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Bitcoin wallet MCP server, apply this rule, and every stx_read_contract call is checked against it from then on.

FAQ

Questions about stx_read_contract

What does the stx_read_contract tool do? +

Read-only call to a Clarity contract function (no transaction needed). 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 stx_read_contract? +

Register the Bitcoin wallet MCP server MCP server in PolicyLayer and add a rule for stx_read_contract: 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 stx_read_contract? +

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

Can I rate-limit stx_read_contract? +

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

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

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

KEEP EXPLORING

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

This server

All 93 Bitcoin wallet MCP server tools →

Across the catalogue

read_input_file on 0gzk →claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →