create_comment
Comment on a post as the board team, optionally replying to a comment.
This record as markdown: /tools/com-featurejet-feedback-board/create-comment.md
What create_comment does on FeatureJet
AI agents use create_comment 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 | string | Yes | |
slug | string | Yes | |
post_id | integer | Yes | |
parent_comment_id | object | — |
Parameters from the server's own tool schema.
Why create_comment is rated Medium
This tool creates new content (a comment) without irreversible consequences, fits the Write category definition of 'creates or modifies data reversibly.' The blast radius is minimal since comments are typically non-destructive, user-facing feedback on a feedback board platform. Severity is low because misuse would result in unwanted comments rather than data loss or system compromise.
From the tool's definition Tool name 'create_comment' and description stating it comments 'on a post' indicates creation of new data (a comment). The description specifies it is a reversible action—commenting can be edited or deleted later.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs create_comment 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_comment, this is the rule to start with:
create_comment 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_comment call is checked against it from then on.
Questions about create_comment
Comment on a post as the board team, optionally replying to a comment. 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_comment accepts 4 parameters: body, slug, post_id, parent_comment_id. Required: body, 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 create_comment: 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_comment 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_comment 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_comment. 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_comment 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