record_dispatch

Record who is actively working an In Progress ticket: appended as a

SERVERFeatureBoard SOURCEhttps://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-featureboard-featureboard/record-dispatch.md

WHAT IT DOES

What record_dispatch does on FeatureBoard

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

RISK

Why record_dispatch is rated Medium

This tool creates or modifies tracking data (recording active worker assignments) without destructive effects. It writes state to the project board but does not execute external operations, delete data, or affect financial systems. The impact is limited to ticket metadata in a local-first project board.

From the tool's definition Tool name 'record_dispatch' and description indicate it appends/records data about who is actively working a ticket. The verb 'appended as a' shows reversible data modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs record_dispatch 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 record_dispatch, this is the rule to start with:

record_dispatch Rate-limited

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

FAQ

Questions about record_dispatch

What does the record_dispatch tool do? +

Record who is actively working an In Progress ticket: appended as a. It is categorised as a Write tool in the FeatureBoard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on record_dispatch? +

Register the FeatureBoard MCP server in PolicyLayer and add a rule for record_dispatch: 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.

What risk level is record_dispatch? +

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

Can I rate-limit record_dispatch? +

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

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

record_dispatch 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.

KEEP EXPLORING

More on FeatureBoard, and thousands of servers like it.

This server

All 215 FeatureBoard tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_record_checkpoint on Team Manager MCP → The MCP Attack Database →

Guides

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