stackspot_start_pot

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/stackspot-start-pot.md

WHAT IT DOES

What stackspot_start_pot does on Aibtc

AI agents invoke stackspot_start_pot 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.

RISK

Why stackspot_start_pot is rated High

This tool executes a blockchain transaction through a smart contract, triggering stacking operations. While not destructive (data is not deleted), it is an Execute-category tool because it: (1) initiates a state-changing operation on an external system (the Stackspots platform contract), (2) has time-sensitive constraints ('must be made during the PoX prepare phase'), and (3) produces irreversible effects (stacking…

From the tool's definition Tool description states 'Trigger a full Stackspot pot to begin stacking via the platform contract' and 'This call goes through the platform contract (stackspots)' — indicates execution of a blockchain contract function with external effects that cannot be…

Attacks that exploit this kind of access

RECOMMENDED RULE

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

stackspot_start_pot Rate-limited

stackspot_start_pot 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stackspot_start_pot": {
      "limits": [
        {
          "counter": "stackspot_start_pot_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about stackspot_start_pot

What does the stackspot_start_pot tool do? +

Trigger a full Stackspot pot to begin stacking via the platform contract. Initiates stacking for a pot that has reached its participant limit. This call goes through the platform contract (stackspots) and must be made during the PoX prepare phase. Any participant can call this once the pot is full. Use a bare contract name (e.g.,. 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.

How do I enforce a policy on stackspot_start_pot? +

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

stackspot_start_pot is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit stackspot_start_pot? +

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

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

stackspot_start_pot 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 → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP →start_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →