# flight_plan

ROKHA'S FLIGHT PLAN — ONE MILESTONE MAP, AS DATA. milestones leads: the Intel® Partner Alliance, IBM Partner Plus and the Microsoft AI Cloud Partner Program CROSSED (three official partnerships), then NEXT IN FOCUS: 1. NVIDIA (in flight — a pursuit, not a partner). Then every other platform program, program, hackathon, grant, integration and directory Rokha is pursuing, and the launch notes (roadmap: live today · opening next · on the horizon) — each pursuit with its status (ON RADAR = pursuing, IN FLIGHT = applied or in progress, LANDED = done), a one-line blurb, WHY IT FITS the platform, and its official link where one exists. Optional track (programs · partner-programs · events · grants · partners · directories; a prefix works) and query (words to match, e.g. 'hackathon', 'IBM', 'Solana grant'). A radar item is a pursuit, never a partnership — only LANDED items are real. Same data as GET https://rokha.ai/api/roadmap and rokha.ai/news/roadmap. Public, no auth.

Agent View of the PolicyLayer registry record for `flight_plan`. HTML page: https://policylayer.com/tools/ai-rokha-rokha/flight-plan

## Facts

- Tool: `flight_plan`
- Server: Rokha (`https://rokha.ai/mcp/jsonrpc`) — https://policylayer.com/tools/ai-rokha-rokha.md
- Homepage: https://github.com/aetherBytes/rokha-sdk
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 2
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `query` | string | no | Words to match across titles, blurbs and fits, e.g. 'hackathon' or 'IBM'. |
| `track` | string | no | One track by key or name (prefix ok): programs, partner-programs, events, grants, partners, directories, token. |

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": "flight_plan",
    "arguments": {}
  }
}
```

## Why flight_plan is rated Medium

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

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

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

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "flight_plan": {
      "limits": [
        {
          "counter": "flight_plan_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Rokha (215)

- `adspace_bid_cancel` — Destructive — https://policylayer.com/tools/ai-rokha-rokha/adspace-bid-cancel.md
- `delete_harness` — Destructive — https://policylayer.com/tools/ai-rokha-rokha/delete-harness.md
- `hook_delete` — Destructive — https://policylayer.com/tools/ai-rokha-rokha/hook-delete.md
- `rig_node_remove` — Destructive — https://policylayer.com/tools/ai-rokha-rokha/rig-node-remove.md
- `schedule_delete` — Destructive — https://policylayer.com/tools/ai-rokha-rokha/schedule-delete.md
- `signet_paper_reset` — Destructive — https://policylayer.com/tools/ai-rokha-rokha/signet-paper-reset.md
- `signet_revoke` — Destructive — https://policylayer.com/tools/ai-rokha-rokha/signet-revoke.md
- `auth_wallet_verify` — Execute — https://policylayer.com/tools/ai-rokha-rokha/auth-wallet-verify.md
- `harness_author` — Execute — https://policylayer.com/tools/ai-rokha-rokha/harness-author.md
- `orbitx__orbitx_gc_focus` — Execute — https://policylayer.com/tools/ai-rokha-rokha/orbitx--orbitx-gc-focus.md
- `registry_adopt` — Execute — https://policylayer.com/tools/ai-rokha-rokha/registry-adopt.md
- `registry_list_server` — Execute — https://policylayer.com/tools/ai-rokha-rokha/registry-list-server.md
- `rig_author` — Execute — https://policylayer.com/tools/ai-rokha-rokha/rig-author.md
- `rig_run` — Execute — https://policylayer.com/tools/ai-rokha-rokha/rig-run.md
- `sandbox_exec` — Execute — https://policylayer.com/tools/ai-rokha-rokha/sandbox-exec.md
- `sandbox_start` — Execute — https://policylayer.com/tools/ai-rokha-rokha/sandbox-start.md
- `sandbox_stop` — Execute — https://policylayer.com/tools/ai-rokha-rokha/sandbox-stop.md
- `send_agent_message` — Execute — https://policylayer.com/tools/ai-rokha-rokha/send-agent-message.md
- `signet_approve` — Execute — https://policylayer.com/tools/ai-rokha-rokha/signet-approve.md
- `singularityagent__mesh` — Execute — https://policylayer.com/tools/ai-rokha-rokha/singularityagent--mesh.md
- `studio_doors` — Execute — https://policylayer.com/tools/ai-rokha-rokha/studio-doors.md
- `x_link_start` — Execute — https://policylayer.com/tools/ai-rokha-rokha/x-link-start.md
- `adnet_feed` — Financial — https://policylayer.com/tools/ai-rokha-rokha/adnet-feed.md
- `adnet_join` — Financial — https://policylayer.com/tools/ai-rokha-rokha/adnet-join.md
- `ads_order` — Financial — https://policylayer.com/tools/ai-rokha-rokha/ads-order.md
- `adspace_bid` — Financial — https://policylayer.com/tools/ai-rokha-rokha/adspace-bid.md
- `auth_wallet_challenge` — Financial — https://policylayer.com/tools/ai-rokha-rokha/auth-wallet-challenge.md
- `campaign_claim` — Financial — https://policylayer.com/tools/ai-rokha-rokha/campaign-claim.md
- `carry_order` — Financial — https://policylayer.com/tools/ai-rokha-rokha/carry-order.md
- `creator_earnings` — Financial — https://policylayer.com/tools/ai-rokha-rokha/creator-earnings.md
- …and 185 more: https://policylayer.com/tools/ai-rokha-rokha.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=ai-rokha-rokha · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/ai-rokha-rokha