This record as markdown: /tools/io-github-bitsandtea-postking-mcp/schedule-post.md
What schedule_post does on Postking Mcp
AI agents use schedule_post 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 schedule_post is rated Medium
Scheduling a post creates or modifies scheduling metadata reversibly—it does not execute immediate publication, delete content, or move money. This is a Write operation (creates scheduling records). Severity is medium because misuse could flood a brand's content calendar with unwanted scheduled posts, but the effect is reversible (posts can be unscheduled or deleted before publication).
From the tool's definition Tool named 'schedule_post' on a content management server (PostKing) alongside 'approve_post' and 'publishing blogs' functionality.
Attacks that exploit this kind of access
The rule that runs schedule_post 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 schedule_post, this is the rule to start with:
schedule_post 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 schedule_post call is checked against it from then on.
Questions about schedule_post
schedule_post is a write tool on the Postking MCP server. 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 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 Postking Mcp. Nothing to install.
schedule_post 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 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.
Set action: deny in the PolicyLayer policy for 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.
schedule_post 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