resolve_review_comment
Mark a review comment resolved by its id (RC-<n>). Idempotent. Once every comment on a ticket is resolved it stops surfacing in the work packet and (if in Review) leaves next_task
This record as markdown: /tools/ai-featureboard-featureboard/resolve-review-comment.md
What resolve_review_comment does on FeatureBoard
AI agents use resolve_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 resolve_review_comment is rated Medium
This tool modifies the status/resolution state of a review comment, which is a reversible write operation. It does not delete data, execute arbitrary code, or have financial impact. The idempotent nature and the fact that resolution state can be toggled confirms this is a Write rather than Destructive action.
From the tool's definition Tool description states 'Mark a review comment resolved by its id' — a state-change operation that updates metadata on a comment object. The operation is idempotent (reversible via unmarking or re-opening), not destructive.
Attacks that exploit this kind of access
The rule that runs resolve_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 resolve_review_comment, this is the rule to start with:
resolve_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 resolve_review_comment call is checked against it from then on.
Questions about resolve_review_comment
Mark a review comment resolved by its id (RC-<n>). Idempotent. Once every comment on a ticket is resolved it stops surfacing in the work packet and (if in Review) leaves next_task. 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 resolve_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.
resolve_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 resolve_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 resolve_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.
resolve_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