# get_launch_status

Lifecycle status of a custom launch from the v4 API, including walletHandoffUrl once the launch reaches authorized. States: received, validating, action_required, authorized, awaiting_wallet_signature, wallet_action_required, submitted, sequencer_soft_confirmed, ethereum_posted, finalized, failed. REQUIRES an API key in PROGRAMMABLE_API_KEY.

Agent View of the PolicyLayer registry record for `get_launch_status`. HTML page: https://policylayer.com/tools/aabxtract-programmable-mcp-server/get-launch-status

## Facts

- Tool: `get_launch_status`
- Server: Programmable (`@aabxtract/programmable-mcp-server`) — https://policylayer.com/tools/aabxtract-programmable-mcp-server.md
- Install: `npx -y @aabxtract/programmable-mcp-server`
- Homepage: https://www.npmjs.com/package/@aabxtract/programmable-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 2 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `chainId` | integer | no | Chain to query. Defaults to 4663 (Robinhood Chain). Use 1 for Ethereum Mainnet. |
| `launchId` | string | yes | Custom launch id. |

Parameters from the server's own tool schema.

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_launch_status",
    "arguments": {
      "launchId": "<launchId>"
    }
  }
}
```

## Why get_launch_status is rated Low

Even though get_launch_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call get_launch_status to retrieve information from Programmable without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_launch_status": {}
  }
}
```

## Other tools on Programmable (8)

- `check_submission_gate` — Read — https://policylayer.com/tools/aabxtract-programmable-mcp-server/check-submission-gate.md
- `get_launch` — Read — https://policylayer.com/tools/aabxtract-programmable-mcp-server/get-launch.md
- `get_modules_by_family` — Read — https://policylayer.com/tools/aabxtract-programmable-mcp-server/get-modules-by-family.md
- `get_stock_paired_launches` — Read — https://policylayer.com/tools/aabxtract-programmable-mcp-server/get-stock-paired-launches.md
- `list_custom_launches` — Read — https://policylayer.com/tools/aabxtract-programmable-mcp-server/list-custom-launches.md
- `list_launches` — Read — https://policylayer.com/tools/aabxtract-programmable-mcp-server/list-launches.md
- `list_modules` — Read — https://policylayer.com/tools/aabxtract-programmable-mcp-server/list-modules.md
- `verify_token` — Read — https://policylayer.com/tools/aabxtract-programmable-mcp-server/verify-token.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=aabxtract-programmable-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/aabxtract-programmable-mcp-server