delete_youtube_report_job
Stop a YouTube bulk reporting job. IRREVERSIBLE IN A WAY THAT IS EASY TO MISS: the job IS the history — deleting it discards every daily CSV it has accumulated, and a replacement job starts over with only a 30-day backfill, so anything older than that is gone for good. Call WITHOUT confirm first:...
This record as markdown: /tools/hermoso/delete-youtube-report-job.md
What delete_youtube_report_job does on Hermoso
AI agents call delete_youtube_report_job to permanently remove resources in Hermoso, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_youtube_report_job is rated Critical
An AI agent that decides to call delete_youtube_report_job doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Hermoso is gone. There is no undo for destructive operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs delete_youtube_report_job safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hermoso, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_youtube_report_job, this is the rule to start with:
delete_youtube_report_job 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 Hermoso, apply this rule, and every delete_youtube_report_job call is checked against it from then on.
Questions about delete_youtube_report_job
Stop a YouTube bulk reporting job. IRREVERSIBLE IN A WAY THAT IS EASY TO MISS: the job IS the history — deleting it discards every daily CSV it has accumulated, and a replacement job starts over with only a 30-day backfill, so anything older than that is gone for good. Call WITHOUT confirm first: nothing is deleted and you get the real job read back from YouTube (its report type and when it was scheduled) to show the user. Then call again with confirm:true. Needs a connected YouTube channel. It is categorised as a Destructive tool in the Hermoso MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hermoso MCP server in PolicyLayer and add a rule for delete_youtube_report_job: 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 Hermoso. Nothing to install.
delete_youtube_report_job 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 delete_youtube_report_job 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 delete_youtube_report_job. 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.
delete_youtube_report_job is provided by the Hermoso MCP server (https://app.hermoso.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hermoso, and thousands of servers like it.
Across the catalogue