opus_schedule_post

Schedule a clip for future publishing.

SERVERFreshdesk SOURCE@mindstone-engineering/mcp-server-freshdesk
Medium RISK CLASS
Category Write
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-schedule-post.md

What opus_schedule_post does on Freshdesk

AI agents use opus_schedule_post to create or update resources in Freshdesk, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freshdesk environment.

Why opus_schedule_post is rated Medium

This tool creates or modifies scheduled content publication, which is a Write operation. It's not Read (no data retrieval), not Execute/Destructive (scheduling is reversible), and not Financial. Severity is medium because misuse could lead to unintended public content publication or schedule conflicts, but the impact is limited to content scheduling without data loss or financial harm.

From the tool's definition Tool name 'opus_schedule_post' and description 'Schedule a clip for future publishing' indicate creation/modification of publishing schedules. The action is reversible (can unschedule or reschedule posts).

Questions about opus_schedule_post

What does the opus_schedule_post tool do? +

Schedule a clip for future publishing. It is categorised as a Write tool in the Freshdesk MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on opus_schedule_post? +

Register the Freshdesk MCP server in PolicyLayer and add a rule for opus_schedule_post: 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_schedule_post? +

opus_schedule_post is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit opus_schedule_post? +

Yes. Add a rate_limit block to the opus_schedule_post 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_schedule_post completely? +

Set action: deny in the PolicyLayer policy for opus_schedule_post. 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_schedule_post? +

opus_schedule_post 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.