schedule_post · Content Automation MCP Server MCP

WHAT IT DOES

What schedule_post does on Content Automation MCP Server

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

WHY IT NEEDS A POLICY

Why schedule_post needs a policy

This tool creates and modifies content on social media platforms (Instagram and Pinterest). While reversible through platform deletion, it commits published or scheduled content to production systems. The high severity reflects that an AI agent misusing this tool could spam, defame, or damage a user's social media presence and brand reputation at scale.

From the tool's definition Tool description explicitly states it is for "creating drafts or scheduling posts to Instagram and Pinterest" and is "the PRIMARY tool for ANY post creation". The tool creates new content on external social media 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 Content Automation MCP Server, so you can run agents against it safely.

FAQ

Questions about schedule_post

What does the schedule_post tool do? +

USE THIS TOOL for creating drafts or scheduling posts to Instagram and Pinterest. This is the PRIMARY tool for ANY post creation (drafts or scheduled). When user asks to. It is categorised as a Write tool in the Content Automation MCP Server 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 Content Automation MCP Server 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 Content Automation MCP Server. 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 Content Automation MCP Server MCP server (ysh-fe/content_automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.