legion_conclude

Settle a proposal and, if it passed, pay the proposer. Permissionless — anyone may

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/legion-conclude.md

WHAT IT DOES

What legion_conclude does on Aibtc

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

RISK

Why legion_conclude is rated Critical

Triggers financial payment to proposer upon proposal settlement; irreversible monetary action.

From the tool's definition Settle a proposal and, if it passed, pay the proposer

Attacks that exploit this kind of access

RECOMMENDED RULE

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

legion_conclude Approval-gated

Any call to legion_conclude 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": {
    "legion_conclude": {
      "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 legion_conclude call is checked against it from then on.

FAQ

Questions about legion_conclude

What does the legion_conclude tool do? +

Settle a proposal and, if it passed, pay the proposer. Permissionless — anyone may. 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 legion_conclude? +

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

legion_conclude 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 legion_conclude? +

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

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

legion_conclude 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 369 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 →