AI agents use account_import 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.
This is a Write operation because it creates/adds a new entry to the address book (a persistent data structure), which is a reversible modification. However, severity is elevated to 'high' rather than medium because the tool handles sensitive authentication material (private keys).
From the tool's definition Tool description states 'Import an existing Hedera account into the address book' and accepts 'account ID, private key, and alias' — this modifies the address book by adding/storing a new entry. The tool reversibly creates a new address book record.
Attacks that exploit this kind of access
Import an existing Hedera account into the address book by providing account ID, private key, and alias. This allows you to manage and reference the account easily. 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 account_import: 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.
account_import 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 account_import 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 account_import. 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.
account_import 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 →