publish_board
Publish a board so it is live at its public URL. OFF BY DEFAULT. Putting a board on the public internet is a human decision: unless the FeatureJet deployment has opted in, this returns 403 publish_disabled and the owner publishes from the dashboard. Where it is enabled it needs a write (or admin)...
This record as markdown: /tools/com-featurejet-feedback-board/publish-board.md
What publish_board does on FeatureJet
AI agents use publish_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 |
|---|---|---|---|
slug | string | Yes |
Parameters from the server's own tool schema.
Why publish_board is rated Medium
This tool creates a public-facing change by making a previously private or unpublished board accessible at its public URL. This is a reversible modification (boards can be unpublished) and represents a Write operation rather than Execute, Destructive, or Financial.
From the tool's definition Tool description states it will 'Publish a board so it is live at its public URL' and requires 'write (or admin) scoped key'. The action of publishing makes a board publicly accessible on the internet.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs publish_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 publish_board, this is the rule to start with:
publish_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 publish_board call is checked against it from then on.
Questions about publish_board
Publish a board so it is live at its public URL. OFF BY DEFAULT. Putting a board on the public internet is a human decision: unless the FeatureJet deployment has opted in, this returns 403 publish_disabled and the owner publishes from the dashboard. Where it is enabled it needs a write (or admin) scoped key and an active subscription -- an org without one gets 403 subscription_required. 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.
publish_board accepts 1 parameter: slug. Required: 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 publish_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.
publish_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 publish_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 publish_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.
publish_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