disable_weekly_schedule
Pause the weekly content schedule without deleting it. Re-enable later with enable_weekly_schedule.
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.
Attacks that exploit this kind of access
The rule that runs disable_weekly_schedule safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Postking Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For disable_weekly_schedule, this is the rule to start with:
disable_weekly_schedule 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 Postking Mcp, apply this rule, and every disable_weekly_schedule call is checked against it from then on.
Questions about disable_weekly_schedule
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.
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.
disable_weekly_schedule 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 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.
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.
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.
This server
Across the catalogue