inscribe_child

Create a child inscription - STEP 1: Broadcast commit transaction.\n\n

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/inscribe-child.md

WHAT IT DOES

What inscribe_child does on Aibtc

AI agents use inscribe_child to commit financial operations through Aibtc, usually the final step of a payment, billing, or trading workflow. A call moves real money.

RISK

Why inscribe_child is rated Critical

Broadcasting a commit transaction on a blockchain involves spending cryptocurrency (typically BTC for inscriptions) to commit to on-chain data. This constitutes a financial operation as it irreversibly spends funds on the network. The presence of sibling tools like 'alex_swap', 'bitflow_create_order', and 'bitflow_cancel_order' confirms this is a financial/blockchain context.

From the tool's definition 'inscribe_child' - 'Create a child inscription - STEP 1: Broadcast commit transaction'

Attacks that exploit this kind of access

RECOMMENDED RULE

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

inscribe_child Approval-gated

Any call to inscribe_child is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "inscribe_child": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about inscribe_child

What does the inscribe_child tool do? +

Create a child inscription - STEP 1: Broadcast commit transaction.\n\n. It is categorised as a Financial tool in the Aibtc MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on inscribe_child? +

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

inscribe_child is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit inscribe_child? +

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

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

inscribe_child 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 → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →