Manage Hedera account address book for multi-account workflows. OPERATIONS: - add: Add account to address book (reference only, no private key) - import: Import account WITH private key for transaction signing - list: Show all saved accounts with aliases and metadata - update: Update account nick...
AI agents use addressbook_manage to create or update resources in HashPilot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HashPilot environment.
The addressbook_manage tool primarily performs reversible write operations: adding, updating, and removing account entries in a local address book. However, the 'import' operation that stores private keys for transaction signing elevates the risk, as compromised address books could enable unauthorized blockchain transactions.
From the tool's definition Tool description lists operations including 'import: Import account WITH private key for transaction signing' and 'add: Add account to address book' and 'update: Update account nickname' and 'remove: Remove account from address book'.
Attacks that exploit this kind of access
Manage Hedera account address book for multi-account workflows. OPERATIONS: - add: Add account to address book (reference only, no private key) - import: Import account WITH private key for transaction signing - list: Show all saved accounts with aliases and metadata - update: Update account nickname - remove: Remove account from address book USE THIS FOR: Managing multiple accounts, organizing workflows, quick account reference. It is categorised as a Write tool in the HashPilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the HashPilot MCP server in PolicyLayer and add a rule for addressbook_manage: 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 HashPilot. Nothing to install.
addressbook_manage 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 addressbook_manage 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 addressbook_manage. 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.
addressbook_manage is provided by the HashPilot MCP server (justmert/hashpilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →