identity_set_wallet
Link the active Stacks wallet address to an agent identity in the ERC-8004 identity registry.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/identity-set-wallet.md
What identity_set_wallet does on Aibtc
AI agents use identity_set_wallet to create or update resources in Aibtc, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aibtc environment.
Why identity_set_wallet is rated Medium
This tool creates or modifies data in the identity registry by linking a wallet address to an agent identity. While it does not delete data or move funds directly, it reversibly writes/updates state in a registry system.
From the tool's definition Tool name includes 'set' and description states 'Link the active Stacks wallet address to an agent identity in the ERC-8004 identity registry.' This modifies registry state by associating a wallet with an identity.
Attacks that exploit this kind of access
The rule that runs identity_set_wallet safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For identity_set_wallet, this is the rule to start with:
identity_set_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 Aibtc, apply this rule, and every identity_set_wallet call is checked against it from then on.
Questions about identity_set_wallet
Link the active Stacks wallet address to an agent identity in the ERC-8004 identity registry. It is categorised as a Write tool in the Aibtc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aibtc MCP server in PolicyLayer and add a rule for identity_set_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 Aibtc. Nothing to install.
identity_set_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 identity_set_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 identity_set_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.
identity_set_wallet is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
This server
Across the catalogue