List all OWS wallets stored locally.
AI agents call ows_list_wallets to retrieve information from Execution Market without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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
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.
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.
ows_list_wallets 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_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.
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.
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.
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 →