# export_wallet

Export the agent

Agent View of the PolicyLayer registry record for `export_wallet`. HTML page: https://policylayer.com/tools/abcxz-conviction-fm/export-wallet

## Facts

- Tool: `export_wallet`
- Server: Conviction (`abcxz/conviction-fm`) — https://policylayer.com/tools/abcxz-conviction-fm.md
- Homepage: https://github.com/abcxz/conviction-fm
- Risk category: Financial (Critical risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Approval-gated

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "export_wallet",
    "arguments": {}
  }
}
```

## Why export_wallet is rated Critical

This server is explicitly financial (trading, positions, revenue pools). An 'export_wallet' tool on such a server almost certainly exports private keys or wallet credentials for an agent that holds or transacts financial assets. Exporting a wallet is a critical financial/security risk: it exposes cryptographic keys that could allow full control over funds.

From the tool's own definition: "'Export the agent' in context of a server that 'makes money', 'opens positions', and 'captures revenue from competition pools' — wallet export implies extracting private keys or credentials tied to financial assets"

## Use case

AI agents use export_wallet to commit financial operations through Conviction, usually the final step of a payment, billing, or trading workflow. A call moves real money.

## Recommended policy (PolicyLayer)

Verdict: **Approval-gated**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Conviction:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_wallet": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}
```

## Other tools on Conviction (9)

- `toggle_agent` — Execute — https://policylayer.com/tools/abcxz-conviction-fm/toggle-agent.md
- `create_agent` — Financial — https://policylayer.com/tools/abcxz-conviction-fm/create-agent.md
- `enter_position` — Financial — https://policylayer.com/tools/abcxz-conviction-fm/enter-position.md
- `get_agent_status` — Read — https://policylayer.com/tools/abcxz-conviction-fm/get-agent-status.md
- `get_leaderboard` — Read — https://policylayer.com/tools/abcxz-conviction-fm/get-leaderboard.md
- `get_my_agents` — Read — https://policylayer.com/tools/abcxz-conviction-fm/get-my-agents.md
- `get_pool_history` — Read — https://policylayer.com/tools/abcxz-conviction-fm/get-pool-history.md
- `get_pools` — Read — https://policylayer.com/tools/abcxz-conviction-fm/get-pools.md
- `update_strategy` — Write — https://policylayer.com/tools/abcxz-conviction-fm/update-strategy.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=abcxz-conviction-fm · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/abcxz-conviction-fm