This record as markdown: /tools/minhoyoo-iotrust-waiaas/transfer-nft.md
What transfer_nft does on Waiaas
AI agents use transfer_nft to commit financial operations through Waiaas, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why transfer_nft is rated Critical
NFT transfers on a blockchain are irreversible asset movements with financial value. The server context explicitly lists NFT operations and crypto transfers. While the description is empty (lowering confidence), the tool name and server context strongly imply an on-chain NFT transfer, which commits a financial asset. Financial > Destructive applies here as it moves a valuable asset permanently.
From the tool's definition Tool name 'transfer_nft' on a server described as handling 'multi-chain crypto operations: transfers, token management, DeFi, NFT, smart contracts'. NFT transfers move blockchain assets irreversibly between addresses.
Attacks that exploit this kind of access
The rule that runs transfer_nft safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Waiaas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For transfer_nft, this is the rule to start with:
Any call to transfer_nft is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Waiaas, apply this rule, and every transfer_nft call is checked against it from then on.
Questions about transfer_nft
transfer_nft is a financial tool on the Waiaas MCP server. It is categorised as a Financial tool in the Waiaas MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Waiaas MCP server in PolicyLayer and add a rule for transfer_nft: 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 Waiaas. Nothing to install.
transfer_nft is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the transfer_nft 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 transfer_nft. 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.
transfer_nft is provided by the Waiaas MCP server (minhoyoo-iotrust/waiaas). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Waiaas, and thousands of servers like it.
Across the catalogue