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...
This record as markdown: /tools/aabxtract-programmable-mcp-server/get-launch-status.md
What get_launch_status does on Programmable
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
chainId | integer | — | 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.
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.
Attacks that exploit this kind of access
The rule that runs get_launch_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Programmable, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_launch_status, this is the rule to start with:
get_launch_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Programmable, apply this rule, and every get_launch_status call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Programmable MCP Server, which means it retrieves data without modifying state.
get_launch_status accepts 2 parameters: chainId, launchId. Required: launchId. The full parameter table on this page comes from the server's own tool schema.
Register the Programmable MCP server in PolicyLayer and add a rule for get_launch_status: 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 Programmable. Nothing to install.
get_launch_status 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 get_launch_status 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 get_launch_status. 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.
get_launch_status is provided by the Programmable MCP server (@aabxtract/programmable-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Programmable, and thousands of servers like it.
This server
Across the catalogue