ows_import_wallet

Import an existing private key into OWS. The key is encrypted and stored locally.

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

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/market-execution-execution-market/ows-import-wallet.md

WHAT IT DOES

What ows_import_wallet does on Execution Market

AI agents use ows_import_wallet to create or update resources in Execution Market, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Execution Market environment.

RISK

Why ows_import_wallet is rated Medium

An AI agent can call ows_import_wallet faster than any human can review: one bad instruction and it creates or modifies resources in Execution Market by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

ows_import_wallet Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ows_import_wallet": {
      "limits": [
        {
          "counter": "ows_import_wallet_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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_import_wallet call is checked against it from then on.

FAQ

Questions about ows_import_wallet

What does the ows_import_wallet tool do? +

Import an existing private key into OWS. The key is encrypted and stored locally. It is categorised as a Write tool in the Execution Market MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ows_import_wallet? +

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

What risk level is ows_import_wallet? +

ows_import_wallet is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit ows_import_wallet? +

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

How do I block ows_import_wallet completely? +

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

What MCP server provides ows_import_wallet? +

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

KEEP EXPLORING

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

This server

All 81 Execution Market tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →