create_board
Create a new feedback board, as a DRAFT. slug is the board's URL path segment (lowercase, hyphenated, unique); name is the display name. The new board's public URL 404s until a human publishes it from the dashboard -- publish_board is off by default (403 publish_disabled).
This record as markdown: /tools/com-featurejet-feedback-board/create-board.md
What create_board does on FeatureJet
AI agents use create_board to create or update resources in FeatureJet, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FeatureJet environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | |
slug | string | Yes | |
description | object | — |
Parameters from the server's own tool schema.
Why create_board is rated Medium
This tool creates a new board resource in a draft state, which is a reversible write operation. The board is not immediately published (remains a 404 to users), and the operation can be undone (deleted via delete_post or similar means). It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition "Create a new feedback board, as a DRAFT" and parameters `slug` and `name` indicate the tool creates new data (a feedback board resource) that is stored and can be subsequently modified or published.
Attacks that exploit this kind of access
The rule that runs create_board safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureJet, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_board, this is the rule to start with:
create_board 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.
The button opens the PolicyLayer dashboard: create your workspace, connect FeatureJet, apply this rule, and every create_board call is checked against it from then on.
Questions about create_board
Create a new feedback board, as a DRAFT. slug is the board's URL path segment (lowercase, hyphenated, unique); name is the display name. The new board's public URL 404s until a human publishes it from the dashboard -- publish_board is off by default (403 publish_disabled). It is categorised as a Write tool in the FeatureJet MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_board accepts 3 parameters: name, slug, description. Required: name, slug. The full parameter table on this page comes from the server's own tool schema.
Register the FeatureJet MCP server in PolicyLayer and add a rule for create_board: 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 FeatureJet. Nothing to install.
create_board is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_board 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 create_board. 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.
create_board is provided by the FeatureJet MCP server (https://mcp.featurejet.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FeatureJet, and thousands of servers like it.
This server
Across the catalogue