Activate a wallet for this MCP connection. All write tools will sign with this account until the connection closes or set_wallet is called again. Overrides the wallet_index parameter on all tools. No restart needed.
AI agents use set_wallet to create or update resources in Question Market — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Question Market environment.
This is a Write operation because it modifies the connection state (sets the active wallet) that affects subsequent operations. While it doesn't directly create or modify data on-chain, it changes which account will authorize future transactions.
From the tool's definition Tool description states 'Activate a wallet for this MCP connection' and 'All write tools will sign with this account until the connection closes or set_wallet is called again.' This modifies the active wallet state for the connection, affecting which account…
Attacks that exploit this kind of access
Activate a wallet for this MCP connection. All write tools will sign with this account until the connection closes or set_wallet is called again. Overrides the wallet_index parameter on all tools. No restart needed. It is categorised as a Write tool in the Question Market MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Question Market MCP server in PolicyLayer and add a rule for 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 Question Market. Nothing to install.
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 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 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.
set_wallet is provided by the Question Market MCP server (qmrkt/mcp-server). 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 →