Create up to 50 posts in one PostEverywhere API call (counts as ONE API-rate-limit hit instead of 50). Each post goes through the same validation as create_post. Returns per-item success/error so you can handle partial failures. Use this for bulk scheduling workflows.
AI agents use bulk_create_posts 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.
This tool creates and publishes social media posts to multiple platforms (Instagram, TikTok, YouTube, LinkedIn, Facebook, X, Threads, Pinterest). Creation is reversible via delete_post, placing it in the Write category rather than Destructive.
From the tool's definition Tool description states 'Create up to 50 posts' and 'goes through the same validation as create_post.' The name and description explicitly indicate post creation across multiple social media platforms, which modifies data (publishes posts) reversibly.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Create up to 50 posts in one PostEverywhere API call (counts as ONE API-rate-limit hit instead of 50). Each post goes through the same validation as create_post. Returns per-item success/error so you can handle partial failures. Use this for bulk scheduling workflows. 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.
Register the Posteverywhere MCP server in PolicyLayer and add a rule for bulk_create_posts: 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.
bulk_create_posts 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 bulk_create_posts 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 bulk_create_posts. 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.
bulk_create_posts 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →