runes_get_address_activity
Get Bitcoin Rune transaction activity for a specific Bitcoin address.\n\n
This record as markdown: /tools/io-github-aibtcdev-mcp-server/runes-get-address-activity.md
What runes_get_address_activity does on Aibtc
AI agents call runes_get_address_activity to retrieve information from Aibtc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why runes_get_address_activity is rated Low
This tool retrieves or queries transaction activity data from a blockchain, which is a Read operation. It has no side effects, does not execute code or commands, does not modify data, and does not move funds. The severity is low because querying public blockchain data poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'runes_get_address_activity' and description 'Get Bitcoin Rune transaction activity for a specific Bitcoin address' indicate a read-only query operation that retrieves historical transaction data without modifying state.
Attacks that exploit this kind of access
The rule that runs runes_get_address_activity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For runes_get_address_activity, this is the rule to start with:
runes_get_address_activity is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every runes_get_address_activity call is checked against it from then on.
Questions about runes_get_address_activity
Get Bitcoin Rune transaction activity for a specific Bitcoin address.\n\n. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.
Register the Aibtc MCP server in PolicyLayer and add a rule for runes_get_address_activity: 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 Aibtc. Nothing to install.
runes_get_address_activity is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the runes_get_address_activity 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.
Set action: deny in the PolicyLayer policy for runes_get_address_activity. 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.
runes_get_address_activity is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
This server
Across the catalogue