AI agents use token_kyc_grant 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 tool modifies the KYC status of an account on the Hedera blockchain, enabling token transfers for that account. It is a reversible write operation (KYC can be revoked), but carries high severity because granting KYC status unlocks financial token transfer capabilities and could be misused to authorize accounts that should not be permitted to transact with regulated tokens.
From the tool's definition Grant KYC (Know Your Customer) status to an account for a token. Required when KYC key is enabled on token to allow transfers.
Attacks that exploit this kind of access
Grant KYC (Know Your Customer) status to an account for a token. Required when KYC key is enabled on token to allow transfers. Operator must have the KYC key. 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 token_kyc_grant: 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.
token_kyc_grant 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 token_kyc_grant 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 token_kyc_grant. 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.
token_kyc_grant 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 →