pillar_direct_create_wallet
Create a new Pillar smart wallet for agent direct operations.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/pillar-direct-create-wallet.md
What pillar_direct_create_wallet does on Aibtc
AI agents use pillar_direct_create_wallet 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.
Why pillar_direct_create_wallet is rated Medium
This tool creates a new smart wallet, which is a Write operation (reversible data creation). However, the severity is elevated to 'high' rather than 'medium' because: (1) wallets are financial infrastructure that, once created and funded, enable financial transactions; (2) an AI agent creating wallets without authorization could facilitate unauthorized financial access; (3) wallet creation is typically a sensitive…
From the tool's definition Tool name and description: 'Create a new Pillar smart wallet for agent direct operations' — the verb 'Create' and the context of generating a new wallet indicates persistent data creation.
Attacks that exploit this kind of access
The rule that runs pillar_direct_create_wallet 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_direct_create_wallet, this is the rule to start with:
pillar_direct_create_wallet 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every pillar_direct_create_wallet call is checked against it from then on.
Questions about pillar_direct_create_wallet
Create a new Pillar smart wallet for agent direct operations. 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.
Register the Aibtc MCP server in PolicyLayer and add a rule for pillar_direct_create_wallet: 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.
pillar_direct_create_wallet is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pillar_direct_create_wallet 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 pillar_direct_create_wallet. 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.
pillar_direct_create_wallet 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.
This server
Across the catalogue