opus_create_censor_job

Create a censor job that processes a specific clip and bleeps / mutes profanity.

SERVERFreshdesk SOURCE@mindstone-engineering/mcp-server-freshdesk
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/freshdesk/opus-create-censor-job.md

What opus_create_censor_job does on Freshdesk

AI agents invoke opus_create_censor_job to trigger actions in Freshdesk. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why opus_create_censor_job is rated High

This tool triggers an external media processing operation (censoring/bleeping a clip), which constitutes executing an external process with side effects. It is not a simple write of data but an active transformation/processing job on media content. Confidence is moderate because this tool seems out of place on a Freshdesk server, but the description is clear about what it does.

From the tool's definition Create a censor job that processes a specific clip and bleeps / mutes profanity

Questions about opus_create_censor_job

What does the opus_create_censor_job tool do? +

Create a censor job that processes a specific clip and bleeps / mutes profanity. It is categorised as a Execute tool in the Freshdesk MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on opus_create_censor_job? +

Register the Freshdesk MCP server in PolicyLayer and add a rule for opus_create_censor_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 Freshdesk. Nothing to install.

What risk level is opus_create_censor_job? +

opus_create_censor_job is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit opus_create_censor_job? +

Yes. Add a rate_limit block to the opus_create_censor_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.

How do I block opus_create_censor_job completely? +

Set action: deny in the PolicyLayer policy for opus_create_censor_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.

What MCP server provides opus_create_censor_job? +

opus_create_censor_job is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Freshdesk, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Freshdesk's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.