flight_plan

SERVERRokha SOURCEhttps://rokha.ai/mcp/jsonrpc

Medium RISK CLASS

Category Write

Parameters 20 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-rokha-rokha/flight-plan.md

WHAT IT DOES

What flight_plan does on Rokha

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.

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

Parameters from the server's own tool schema.

RISK

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 signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs flight_plan safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Rokha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For flight_plan, this is the rule to start with:

flight_plan Rate-limited

flight_plan 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": {
    "flight_plan": {
      "limits": [
        {
          "counter": "flight_plan_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 Rokha, apply this rule, and every flight_plan call is checked against it from then on.

FAQ

Questions about flight_plan

What does the flight_plan tool do? +

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. It is categorised as a Write tool in the Rokha MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does flight_plan accept? +

flight_plan accepts 2 parameters: query, track. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on flight_plan? +

Register the Rokha MCP server in PolicyLayer and add a rule for flight_plan: 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 Rokha. Nothing to install.

What risk level is flight_plan? +

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

Can I rate-limit flight_plan? +

Yes. Add a rate_limit block to the flight_plan 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 flight_plan completely? +

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

flight_plan is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Rokha, and thousands of servers like it.

This server

All 216 Rokha tools →

Across the catalogue

poc_plan on 05 Mcp A2a Solution Studio →emit_variant_plan on 0sec → The MCP Attack Database →

Guides

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