pillar_key_generate

Generate a new secp256k1 signing keypair for Pillar smart wallet direct operations.

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

What pillar_key_generate does on Aibtc

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

Why pillar_key_generate is rated High

This tool generates cryptographic key material (a secp256k1 keypair) used for signing smart wallet operations. Key generation is an execution action with significant security implications — the generated private key controls a smart wallet, and misuse (e.g., key exposure or unauthorized generation) could lead to loss of funds or unauthorized access.

From the tool's definition Generate a new secp256k1 signing keypair for Pillar smart wallet direct operations

Questions about pillar_key_generate

What does the pillar_key_generate tool do? +

Generate a new secp256k1 signing keypair for Pillar smart wallet direct operations. 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 pillar_key_generate? +

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

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

Can I rate-limit pillar_key_generate? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Aibtc's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.