youtube_moderate_comment
Apply a moderation status to a YouTube comment. Allowed status values: heldForReview, published, rejected, spam. Costs 50 quota units.
This record as markdown: /tools/io-github-saloprj-dialogbrain/youtube-moderate-comment.md
What youtube_moderate_comment does on Dialogbrain
AI agents use youtube_moderate_comment to create or update resources in Dialogbrain, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dialogbrain environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
status | string | Yes | One of: heldForReview, published, rejected, spam. |
comment_id | string | Yes | Bare commentId OR 'youtube:comment:<id>'. |
Parameters from the server's own tool schema.
Why youtube_moderate_comment is rated Medium
This tool modifies existing data (comment moderation state) without permanently deleting it. The action is reversible—a comment's status can be changed again. While it affects content visibility/availability, it doesn't destroy data or move money. Write is most appropriate as it creates or modifies data reversibly.
From the tool's definition Tool applies a moderation status to a YouTube comment with values: heldForReview, published, rejected, spam. The description explicitly states it modifies comment status, a reversible action.
Attacks that exploit this kind of access
The rule that runs youtube_moderate_comment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For youtube_moderate_comment, this is the rule to start with:
youtube_moderate_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 Dialogbrain, apply this rule, and every youtube_moderate_comment call is checked against it from then on.
Questions about youtube_moderate_comment
Apply a moderation status to a YouTube comment. Allowed status values: heldForReview, published, rejected, spam. Costs 50 quota units. It is categorised as a Write tool in the Dialogbrain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
youtube_moderate_comment accepts 2 parameters: status, comment_id. Required: status, comment_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for youtube_moderate_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 Dialogbrain. Nothing to install.
youtube_moderate_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 youtube_moderate_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 youtube_moderate_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.
youtube_moderate_comment is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue