pillar_disconnect

Disconnect from Pillar. Clears locally stored wallet address.

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Medium RISK CLASS

Category Write

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/pillar-disconnect.md

WHAT IT DOES

What pillar_disconnect does on Aibtc

AI agents use pillar_disconnect to create or update resources in Aibtc, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aibtc environment.

RISK

Why pillar_disconnect is rated Medium

This tool modifies local state by clearing stored wallet information. It is reversible (the wallet address can be re-added), making it a Write operation rather than Destructive. The blast radius is low since it only affects locally cached data and does not irreversibly delete or compromise the wallet itself or financial assets.

From the tool's definition Clears locally stored wallet address - a reversible modification of local state.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pillar_disconnect Rate-limited

pillar_disconnect stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pillar_disconnect": {
      "limits": [
        {
          "counter": "pillar_disconnect_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about pillar_disconnect

What does the pillar_disconnect tool do? +

Disconnect from Pillar. Clears locally stored wallet address. It is categorised as a Write tool in the Aibtc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pillar_disconnect? +

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

pillar_disconnect is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pillar_disconnect? +

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

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

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

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →