add_media_comment
Add a threaded comment to a gallery asset (a discussion thread, distinct from pin annotations). Pass parentId (a comment id from get_media / list_media_comments) to reply to an existing comment. Returns the new comment and total count.
This record as markdown: /tools/ai-featureboard-featureboard/add-media-comment.md
What add_media_comment does on FeatureBoard
AI agents use add_media_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_media_comment is rated Medium
This tool creates new comment data in a gallery/discussion system. It is reversible (comments can typically be deleted or edited later, unlike destructive operations), has no financial impact, and does not execute arbitrary code.
From the tool's definition Tool description: 'Add a threaded comment to a gallery asset' and 'Returns the new comment and total count.' The verb 'Add' and the return of 'the new comment' indicate creation of new data.
Attacks that exploit this kind of access
The rule that runs add_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 add_media_comment, this is the rule to start with:
add_media_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_media_comment call is checked against it from then on.
Questions about add_media_comment
Add a threaded comment to a gallery asset (a discussion thread, distinct from pin annotations). Pass parentId (a comment id from get_media / list_media_comments) to reply to an existing comment. Returns the new comment and total count. 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_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.
add_media_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_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 add_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.
add_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.
This server
Across the catalogue