unset_agent_wallet
Unlink agent wallet from Identity Registry entry
This record as markdown: /tools/minhoyoo-iotrust-waiaas/unset-agent-wallet.md
What unset_agent_wallet does on Waiaas
AI agents use unset_agent_wallet to create or update resources in Waiaas, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Waiaas environment.
Why unset_agent_wallet is rated Medium
This tool removes an association between an agent wallet and an Identity Registry entry. While it doesn't delete the wallet itself, unlinking from an identity registry is a significant write operation that could disrupt agent operations, break authentication/authorization flows, and potentially lock out access to funds.
From the tool's definition Unlink agent wallet from Identity Registry entry
Attacks that exploit this kind of access
The rule that runs unset_agent_wallet 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 unset_agent_wallet, this is the rule to start with:
unset_agent_wallet stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Waiaas, apply this rule, and every unset_agent_wallet call is checked against it from then on.
Questions about unset_agent_wallet
Unlink agent wallet from Identity Registry entry. It is categorised as a Write tool in the Waiaas MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Waiaas MCP server in PolicyLayer and add a rule for unset_agent_wallet: 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.
unset_agent_wallet 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 unset_agent_wallet 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 unset_agent_wallet. 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.
unset_agent_wallet 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.
This server
Across the catalogue