disable_weekly_schedule

Pause the weekly content schedule without deleting it. Re-enable later with enable_weekly_schedule.

SERVERPostking Mcp SOURCEpostking-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-bitsandtea-postking-mcp/disable-weekly-schedule.md

What disable_weekly_schedule does on Postking Mcp

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

Why disable_weekly_schedule is rated Medium

This is classified as Write rather than Execute because it modifies configuration/state (pausing a schedule) rather than triggering an execution. It is reversible via enable_weekly_schedule, so not Destructive. The severity is medium because disabling a content schedule could disrupt a brand's publishing pipeline and business operations, but the impact is limited to pausing rather than deleting, and it can be undone.

From the tool's definition The tool description states it will "pause the weekly content schedule" - this is a state modification operation that changes the active status of a recurring scheduling system.

Questions about disable_weekly_schedule

What does the disable_weekly_schedule tool do? +

Pause the weekly content schedule without deleting it. Re-enable later with enable_weekly_schedule. It is categorised as a Write tool in the Postking Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on disable_weekly_schedule? +

Register the Postking MCP server in PolicyLayer and add a rule for disable_weekly_schedule: 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 Postking Mcp. Nothing to install.

What risk level is disable_weekly_schedule? +

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

Can I rate-limit disable_weekly_schedule? +

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

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

disable_weekly_schedule is provided by the Postking MCP server (postking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Postking, 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 Postking'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.