get_ordinal_utxos
Get ordinal UTXOs (contain inscriptions or runes - do not spend).
This record as markdown: /tools/io-github-aibtcdev-mcp-server/get-ordinal-utxos.md
What get_ordinal_utxos does on Aibtc
AI agents call get_ordinal_utxos 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 get_ordinal_utxos is rated Low
This tool retrieves information about unspent transaction outputs that contain inscriptions or runes on the blockchain. It performs a read-only query with no side effects, data modification, execution of code, or financial operations. The low severity reflects minimal risk if misused by an agent—at worst, it returns blockchain data already public.
From the tool's definition Tool name 'get_ordinal_utxos' and description 'Get ordinal UTXOs' indicate a query/retrieval operation. The phrase 'do not spend' is an instruction to users, not a capability of the tool itself.
Attacks that exploit this kind of access
The rule that runs get_ordinal_utxos 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 get_ordinal_utxos, this is the rule to start with:
get_ordinal_utxos 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 get_ordinal_utxos call is checked against it from then on.
Questions about get_ordinal_utxos
Get ordinal UTXOs (contain inscriptions or runes - do not spend). 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 get_ordinal_utxos: 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.
get_ordinal_utxos 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 get_ordinal_utxos 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 get_ordinal_utxos. 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.
get_ordinal_utxos 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