runes_list_etchings

List all Bitcoin Rune etchings (token deployments) with pagination.\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-list-etchings.md

WHAT IT DOES

What runes_list_etchings does on Aibtc

AI agents call runes_list_etchings 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_list_etchings is rated Low

This tool retrieves and displays information about Bitcoin Rune token deployments with pagination support. It has no side effects, does not modify data, and does not trigger any external operations or financial transactions. The functionality is limited to querying and presenting existing data, making it a Read operation with low severity risk.

From the tool's definition Tool name 'runes_list_etchings' and description 'List all Bitcoin Rune etchings (token deployments) with pagination' indicate a retrieval operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

runes_list_etchings Allowed

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

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_list_etchings call is checked against it from then on.

FAQ

Questions about runes_list_etchings

What does the runes_list_etchings tool do? +

List all Bitcoin Rune etchings (token deployments) with pagination.\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_list_etchings? +

Register the Aibtc MCP server in PolicyLayer and add a rule for runes_list_etchings: 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_list_etchings? +

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

Can I rate-limit runes_list_etchings? +

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

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

runes_list_etchings 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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