next_wave
The PLURAL of next_task: return the whole dispatchable set at once, already partitioned into file-disjoint lanes,
This record as markdown: /tools/ai-featureboard-featureboard/next-wave.md
What next_wave does on FeatureBoard
AI agents call next_wave to retrieve information from FeatureBoard without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why next_wave is rated Low
The description indicates this tool returns (reads) a set of dispatchable tasks partitioned into lanes. There is no indication of creating, modifying, executing, or deleting data. It appears to be a query/planning operation that surfaces the next batch of work items, similar to a read/list operation.
From the tool's definition 'return the whole dispatchable set at once, already partitioned into file-disjoint lanes' — the tool retrieves/returns a set of tasks without indicating any mutation
Attacks that exploit this kind of access
The rule that runs next_wave safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For next_wave, this is the rule to start with:
next_wave 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 FeatureBoard, apply this rule, and every next_wave call is checked against it from then on.
Questions about next_wave
The PLURAL of next_task: return the whole dispatchable set at once, already partitioned into file-disjoint lanes,. It is categorised as a Read tool in the FeatureBoard MCP Server, which means it retrieves data without modifying state.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for next_wave: 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 FeatureBoard. Nothing to install.
next_wave 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 next_wave 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 next_wave. 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.
next_wave is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FeatureBoard, and thousands of servers like it.
This server
Across the catalogue