propose_status
Propose a status change for the board owner to confirm. The agent-honest way to mark work done: nothing changes on the public board and no voter is notified until a human confirms the proposal from the dashboard. status is one of open|planned|in_progress|shipped|declined; a new proposal replaces ...
This record as markdown: /tools/com-featurejet-feedback-board/propose-status.md
What propose_status does on FeatureJet
AI agents use propose_status 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 |
|---|---|---|---|
note | object | — | |
slug | string | Yes | |
status | string | Yes | |
post_id | integer | Yes | |
action_key | object | — |
Parameters from the server's own tool schema.
Why propose_status is rated Medium
Creates a pending proposal; no public change occurs until human confirms.
From the tool's definition Propose a status change for the board owner to confirm
Attacks that exploit this kind of access
The rule that runs propose_status 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 propose_status, this is the rule to start with:
propose_status 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 propose_status call is checked against it from then on.
Questions about propose_status
Propose a status change for the board owner to confirm. The agent-honest way to mark work done: nothing changes on the public board and no voter is notified until a human confirms the proposal from the dashboard. status is one of open|planned|in_progress|shipped|declined; a new proposal replaces any pending one. Prefer this over update_post's direct status flip. 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.
propose_status accepts 5 parameters: note, slug, status, post_id, action_key. Required: slug, status, 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 propose_status: 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.
propose_status 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 propose_status 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 propose_status. 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.
propose_status 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