runes_get_activity

Get recent on-chain activity (mints, transfers, burns) for a specific Bitcoin Rune.\n\n

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/runes-get-activity.md

WHAT IT DOES

What runes_get_activity does on Aibtc

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

RISK

Why runes_get_activity is rated Low

The tool queries and retrieves historical blockchain activity data for a Bitcoin Rune with no side effects, no code execution, and no ability to modify data. This is a straightforward read operation that falls squarely in the Read category with low severity.

From the tool's definition Tool description states 'Get recent on-chain activity (mints, transfers, burns)' — a retrieval operation with no modification or execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs runes_get_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_activity, this is the rule to start with:

runes_get_activity Allowed

runes_get_activity 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": {
    "runes_get_activity": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every runes_get_activity call is checked against it from then on.

FAQ

Questions about runes_get_activity

What does the runes_get_activity tool do? +

Get recent on-chain activity (mints, transfers, burns) for a specific Bitcoin Rune.\n\n. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on runes_get_activity? +

Register the Aibtc MCP server in PolicyLayer and add a rule for runes_get_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.

What risk level is runes_get_activity? +

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

Can I rate-limit runes_get_activity? +

Yes. Add a rate_limit block to the runes_get_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.

How do I block runes_get_activity completely? +

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

What MCP server provides runes_get_activity? +

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

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 358 Aibtc tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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