threads_repost

THE RISK

Medium Risk

Why threads_repost needs a policy

This tool publishes content to a user's profile by reposting an existing thread. It creates a new post/share on the user's profile, which is a reversible write action (the repost can be deleted). Misuse could result in unwanted content being shared publicly on a user's profile, hence medium severity.

From the tool's definition Reposts (shares) an existing thread to your profile

Documented attack patterns abuse exactly the kind of access threads_repost gives an agent:

POLICY

How to control threads_repost

PolicyLayer is an MCP gateway — it sits between your AI agents and Meta MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for threads_repost:

policy.json

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

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

Create a free account and register Meta MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Meta MCP Server tools

Financial meta_create_adset Creates a new ad set within a campaign. Args: - ad_account_id (string): Ad account ID ( Financial meta_create_campaign Creates a new campaign in a Meta ad account. Args: - ad_account_id (string): Ad account Destructive meta_delete_ad Deletes an ad permanently. Args: - ad_id (string): Ad ID to delete Destructive meta_delete_ad_rule Deletes an automated ad rule. Args: - rule_id (string): Ad rule ID Destructive meta_delete_adset Deletes an ad set permanently. Args: - adset_id (string): Ad set ID to delete Destructive meta_delete_campaign Deletes (archives) a campaign. This cannot be undone. Args: - campaign_id (string): Cam Destructive meta_delete_comment Deletes a comment on a Facebook Page post. Permanent action. Args: - comment_id (string Destructive meta_delete_custom_audience Deletes a custom audience permanently. This cannot be undone. Args: - audience_id (stri

All 200 Meta MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about threads_repost

What does the threads_repost tool do? +

Reposts (shares) an existing thread to your profile. Args: - threads_user_id (string): Your Threads user ID - media_id (string): Thread media ID to repost. It is categorised as a Write tool in the Meta 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 threads_repost? +

Register the Meta MCP Server MCP server in PolicyLayer and add a rule for threads_repost: 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 Meta MCP Server. Nothing to install.

What risk level is threads_repost? +

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

Can I rate-limit threads_repost? +

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

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

threads_repost is provided by the Meta MCP Server MCP server (oliverames/meta-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Meta MCP Server tool call.

Start from Meta MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →