ows_get_wallet
Get details of a specific wallet by name or ID, including all chain addresses.
This record as markdown: /tools/market-execution-execution-market/ows-get-wallet.md
What ows_get_wallet does on Execution Market
AI agents call ows_get_wallet to retrieve information from Execution Market without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why ows_get_wallet is rated Low
This tool retrieves wallet information (details and chain addresses) without creating, modifying, deleting, or executing any operations. It is a straightforward read/query operation. While wallet information may be sensitive from a privacy perspective, the tool itself performs no state-changing or privileged action.
From the tool's definition Tool description states 'Get details of a specific wallet by name or ID, including all chain addresses.' The verb 'Get' and the read-only nature of retrieving wallet details without modification confirm this is a query operation.
Attacks that exploit this kind of access
The rule that runs ows_get_wallet safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Execution Market, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ows_get_wallet, this is the rule to start with:
ows_get_wallet is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Execution Market, apply this rule, and every ows_get_wallet call is checked against it from then on.
Questions about ows_get_wallet
Get details of a specific wallet by name or ID, including all chain addresses. It is categorised as a Read tool in the Execution Market MCP Server, which means it retrieves data without modifying state.
Register the Execution Market MCP server in PolicyLayer and add a rule for ows_get_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 Execution Market. Nothing to install.
ows_get_wallet is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ows_get_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 ows_get_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.
ows_get_wallet is provided by the Execution Market MCP server (https://mcp.execution.market/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Execution Market, and thousands of servers like it.
This server
Across the catalogue