schedule_post · Posteverywhere MCP: Risk & Policy

WHAT IT DOES

What schedule_post does on Posteverywhere

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

WHY IT NEEDS A POLICY

Why schedule_post needs a policy

This tool creates new published content on social media platforms, which is a Write operation (reversible via platform deletion tools, but creates real-world artifacts with potential reputational/engagement impact). It is not Destructive because the action is technically reversible by the account owner.

From the tool's definition Tool description states 'Publish or schedule a DRAFT' and 'publish_now: true to publish it right away', confirming it modifies/creates published content on external platforms.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

schedule_post Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "schedule_post": {
      "limits": [
        {
          "counter": "schedule_post_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Posteverywhere, so you can run agents against it safely.

FAQ

Questions about schedule_post

What does the schedule_post tool do? +

Publish or schedule a DRAFT (created with create_post(draft: true)). Pass scheduled_for to schedule it for a future time, or publish_now: true to publish it right away. Optionally pass account_ids to set/override which accounts it posts to (defaults to the accounts saved on the draft). This is the final step of the review workflow: create_post(draft:true) → review with list_posts(status:. It is categorised as a Write tool in the Posteverywhere MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on schedule_post? +

Register the Posteverywhere 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 Posteverywhere. Nothing to install.

What risk level is schedule_post? +

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

Can I rate-limit schedule_post? +

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.

How do I block schedule_post completely? +

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.

What MCP server provides schedule_post? +

schedule_post is provided by the Posteverywhere MCP server (posteverywhere/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.