Posteverywhere

33 tools. 18 can modify or destroy data without limits.

4 destructive tools with no built-in limits. Policy required.

Last updated:

18 can modify or destroy data
15 read-only
33 tools total

Community server · catalogue entry verified 30/06/2026

How to control Posteverywhere ↓

What Posteverywhere exposes to your agents

Read (15) Write / Execute (14) Destructive / Financial (4)
Critical Risk

The most dangerous Posteverywhere tools

18 of Posteverywhere's 33 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Posteverywhere

PolicyLayer is an MCP gateway — it sits between your AI agents and Posteverywhere, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations
{
  "delete_campaign": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "bulk_create_posts": {
    "limits": [
      {
        "counter": "bulk_create_posts_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "get_account": {
    "limits": [
      {
        "counter": "get_account_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Posteverywhere — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON POSTEVERYWHERE →

Instant setup, no code required.

All 33 Posteverywhere tools

READ 15 tools
Read get_account Get detailed information about a specific connected social media account on PostEverywhere. Returns the accoun Read get_account_health Check the health of a connected social account on PostEverywhere. Returns status (healthy|warning|broken), can Read get_analytics_summary Get aggregate posting metrics over a time window on PostEverywhere. Returns counts (scheduled/published/failed Read get_campaign Get details of a single campaign on PostEverywhere by its id, including post_count. Read get_me Get the current API key context on PostEverywhere — who you are, what scopes your key has, what plan the organ Read get_media Get detailed information about a specific media file on PostEverywhere, including its type, dimensions, file s Read get_post Get detailed information about a specific post on PostEverywhere, including its content, media attachments, sc Read get_post_results Get the per-platform publishing results for a specific post on PostEverywhere. Returns detailed status for eac Read get_webhook Get details of a single webhook subscription on PostEverywhere (does NOT include the signing secret). Read list_accounts List all connected social media accounts on PostEverywhere. Returns account IDs, platform names, usernames, an Read list_campaigns List campaigns in the current workspace on PostEverywhere. Campaigns group related posts (e.g., Read list_media List media files in the PostEverywhere media library. Supports filtering by type (image, video, document) and Read list_posts List scheduled, published, or draft posts on PostEverywhere. Supports filtering by status (scheduled, publishe Read list_posts_advanced List posts on PostEverywhere with the FULL set of filters available on the API (since June 2026). Like list_po Read list_webhooks List all webhook subscriptions on PostEverywhere for the current organization. Returns id, url, subscribed eve

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Posteverywhere

Can an AI agent delete data through the Posteverywhere MCP server? +

Yes. The Posteverywhere server exposes 4 destructive tools including delete_campaign, delete_media, delete_post. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Posteverywhere? +

The Posteverywhere server has 11 write tools including bulk_create_posts, create_campaign, create_post. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Posteverywhere.

How many tools does the Posteverywhere MCP server expose? +

33 tools across 3 categories: Destructive, Read, Write. 15 are read-only. 18 can modify, create, or delete data.

How do I enforce a policy on Posteverywhere? +

Register the Posteverywhere MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Posteverywhere tool call.

Deterministic rules across all 33 Posteverywhere tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

33 Posteverywhere tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.