ows_list_wallets

List all OWS wallets stored locally.

SERVERExecution Market SOURCEhttps://mcp.execution.market/mcp/

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/market-execution-execution-market/ows-list-wallets.md

WHAT IT DOES

What ows_list_wallets does on Execution Market

AI agents call ows_list_wallets 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.

RISK

Why ows_list_wallets is rated Low

This tool retrieves wallet information from local storage without modifying, deleting, or executing any operations. It is a pure read operation. Severity is low because listing local wallets does not directly expose financial transaction capabilities, though the information could inform subsequent financial actions by an agent. The confidence is high due to clear, unambiguous description.

From the tool's definition Tool name contains 'list' and description states 'List all OWS wallets stored locally' — a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ows_list_wallets 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_list_wallets, this is the rule to start with:

ows_list_wallets Allowed

ows_list_wallets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ows_list_wallets": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Execution Market, apply this rule, and every ows_list_wallets call is checked against it from then on.

FAQ

Questions about ows_list_wallets

What does the ows_list_wallets tool do? +

List all OWS wallets stored locally. It is categorised as a Read tool in the Execution Market MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ows_list_wallets? +

Register the Execution Market MCP server in PolicyLayer and add a rule for ows_list_wallets: 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.

What risk level is ows_list_wallets? +

ows_list_wallets is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ows_list_wallets? +

Yes. Add a rate_limit block to the ows_list_wallets 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.

How do I block ows_list_wallets completely? +

Set action: deny in the PolicyLayer policy for ows_list_wallets. 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.

What MCP server provides ows_list_wallets? +

ows_list_wallets 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.

KEEP EXPLORING

More on Execution Market, and thousands of servers like it.

This server

All 81 Execution Market tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →