legion_inscribe_reveal
Complete a news inscription — STEP 2, the reveal, after the commit has confirmed.\n\n
This record as markdown: /tools/io-github-aibtcdev-mcp-server/legion-inscribe-reveal.md
What legion_inscribe_reveal does on Aibtc
AI agents invoke legion_inscribe_reveal to trigger actions in Aibtc. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why legion_inscribe_reveal is rated High
This tool executes an on-chain blockchain operation (reveal phase of a commit-reveal inscription). It triggers an external blockchain transaction whose effects are irreversible once broadcast, placing it in the Execute or Destructive category. While inscription data cannot easily be 'deleted', the primary action is executing a blockchain transaction rather than destroying data.
From the tool's definition 'Complete a news inscription — STEP 2, the reveal, after the commit has confirmed.' — triggers an on-chain reveal/inscription operation that finalizes a previously committed transaction
Attacks that exploit this kind of access
The rule that runs legion_inscribe_reveal 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 legion_inscribe_reveal, this is the rule to start with:
legion_inscribe_reveal stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 legion_inscribe_reveal call is checked against it from then on.
Questions about legion_inscribe_reveal
Complete a news inscription — STEP 2, the reveal, after the commit has confirmed.\n\n. It is categorised as a Execute tool in the Aibtc MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aibtc MCP server in PolicyLayer and add a rule for legion_inscribe_reveal: 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.
legion_inscribe_reveal is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the legion_inscribe_reveal 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 legion_inscribe_reveal. 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.
legion_inscribe_reveal 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.
Across the catalogue