remove_media_comment
Remove a comment by id (from get_media / list_media_comments). By default its reply subtree is removed too; set cascade:false to refuse when it still has replies. Returns the ids removed.
This record as markdown: /tools/ai-featureboard-featureboard/remove-media-comment.md
What remove_media_comment does on FeatureBoard
AI agents call remove_media_comment to permanently remove resources in FeatureBoard, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_media_comment is rated Critical
This tool irreversibly deletes data (comments and optionally their reply subtrees) and cannot be undone. Although the blast radius is limited to comment deletion on a local project board rather than core business data, it meets the definition of Destructive. The cascade option allows deletion of dependent records, increasing the potential for unintended data loss if an AI agent misuses it.
From the tool's definition remove_media_comment removes a comment by id. The description states 'By default its reply subtree is removed too', indicating that deletion is irreversible and can cascade to child replies. The tool returns the ids removed, confirming deletion semantics.
Attacks that exploit this kind of access
The rule that runs remove_media_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 remove_media_comment, this is the rule to start with:
remove_media_comment is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every remove_media_comment call is checked against it from then on.
Questions about remove_media_comment
Remove a comment by id (from get_media / list_media_comments). By default its reply subtree is removed too; set cascade:false to refuse when it still has replies. Returns the ids removed. It is categorised as a Destructive tool in the FeatureBoard MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for remove_media_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.
remove_media_comment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_media_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 remove_media_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.
remove_media_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.
Across the catalogue