update_post
Update mutable post fields; null queue_rank explicitly un-ranks.
This record as markdown: /tools/com-featurejet-feedback-board/update-post.md
What update_post does on FeatureJet
AI agents use update_post 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 |
|---|---|---|---|
body | object | — | |
slug | string | Yes | |
tags | object | — | |
title | object | — | |
pinned | object | — | |
status | object | — | |
post_id | integer | Yes | |
queue_rank | object | — |
Parameters from the server's own tool schema.
Why update_post is rated Medium
This tool modifies existing post data (update operation) in a reversible manner. The description indicates it changes mutable fields and queue ranking status, which can be reverted by subsequent updates. While it affects the state of posts on a feedback board, these changes are not destructive or permanent.
From the tool's definition Tool explicitly performs 'Update mutable post fields' and can set queue_rank to null to 'un-rank' posts, indicating reversible modification of data without deletion or irreversible side effects.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs update_post 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 update_post, this is the rule to start with:
update_post 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 update_post call is checked against it from then on.
Questions about update_post
Update mutable post fields; null queue_rank explicitly un-ranks. 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.
update_post accepts 8 parameters: body, slug, tags, title, pinned, status, post_id, queue_rank. Required: slug, post_id. 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 update_post: 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.
update_post 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 update_post 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 update_post. 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.
update_post 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