retry_failed_post · Posteverywhere MCP: Risk & Policy

WHAT IT DOES

What retry_failed_post does on Posteverywhere

AI agents invoke retry_failed_post to trigger actions in Posteverywhere. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why retry_failed_post needs a policy

This tool triggers re-execution of publishing operations by resetting failed posts to queued status and causing the publishing system to re-attempt them. It doesn't just read or write data — it initiates an external operation (social media publishing) across multiple platforms. Misuse could result in unintended posts being published to Instagram, TikTok, YouTube, LinkedIn, Facebook, X, Threads, or Pinterest.

From the tool's definition Retry all failed platform destinations for a specific post... Resets failed destinations back to queued status so they will be re-attempted by the publishing system

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

retry_failed_post Rate-limited

retry_failed_post stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "retry_failed_post": {
      "limits": [
        {
          "counter": "retry_failed_post_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 retry_failed_post

What does the retry_failed_post tool do? +

Retry all failed platform destinations for a specific post on PostEverywhere. Resets failed destinations back to queued status so they will be re-attempted by the publishing system. Use this when a post failed due to temporary issues like rate limits or token expiry (after the token has been refreshed). It is categorised as a Execute tool in the Posteverywhere MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on retry_failed_post? +

Register the Posteverywhere MCP server in PolicyLayer and add a rule for retry_failed_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 retry_failed_post? +

retry_failed_post is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit retry_failed_post? +

Yes. Add a rate_limit block to the retry_failed_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 retry_failed_post completely? +

Set action: deny in the PolicyLayer policy for retry_failed_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 retry_failed_post? +

retry_failed_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.