add_review_comment
Attach a PR-style review comment to a ticket (optionally anchored to a file and line). Unresolved review comments surface in the ticket
This record as markdown: /tools/ai-featureboard-featureboard/add-review-comment.md
What add_review_comment does on FeatureBoard
AI agents use add_review_comment to create or update resources in FeatureBoard, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FeatureBoard environment.
Why add_review_comment is rated Medium
This tool creates or modifies ticket metadata by adding review comments, which are reversible changes to the ticket system. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read). It fits Write because it creates new comments and modifies ticket state.
From the tool's definition Tool description states 'Attach a PR-style review comment' — this creates new comment data on a ticket. The phrase 'Attach' and 'Unresolved review comments surface' indicates persistent creation/modification of ticket state.
Attacks that exploit this kind of access
The rule that runs add_review_comment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_review_comment, this is the rule to start with:
add_review_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 FeatureBoard, apply this rule, and every add_review_comment call is checked against it from then on.
Questions about add_review_comment
Attach a PR-style review comment to a ticket (optionally anchored to a file and line). Unresolved review comments surface in the ticket. It is categorised as a Write tool in the FeatureBoard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for add_review_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 FeatureBoard. Nothing to install.
add_review_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 add_review_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 add_review_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.
add_review_comment is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FeatureBoard, and thousands of servers like it.
This server
Across the catalogue