extend_stacking

Extend an existing stacking lock period.

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/extend-stacking.md

WHAT IT DOES

What extend_stacking does on Aibtc

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

RISK

Why extend_stacking is rated Critical

Stacking in the Stacks blockchain context involves locking STX tokens to earn Bitcoin rewards. Extending a stacking lock period modifies the duration for which cryptocurrency assets are locked/committed, which constitutes a financial obligation — the user's tokens remain locked and unavailable for a longer period. This is a financial action as it affects cryptocurrency asset management and lock-up commitments.

From the tool's definition Extend an existing stacking lock period

Attacks that exploit this kind of access

RECOMMENDED RULE

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

extend_stacking Approval-gated

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

FAQ

Questions about extend_stacking

What does the extend_stacking tool do? +

Extend an existing stacking lock period. 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 extend_stacking? +

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

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

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

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

extend_stacking 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 →