Publishes a text-only post to Threads. Two-step flow: creates a container, then publishes it. Args: - threads_user_id (string): Threads user ID - text (string): Post text (up to 500 characters) - reply_to_id (string, optional): Thread ID to reply to - quote_post_id (string, optional): Thread ID t...
AI agents use threads_publish_text to create or update resources in Meta MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta MCP Server environment.
This tool creates new content on a public platform (Threads) in a reversible manner. While posts can be deleted, the primary action is creation/modification of data. The blast radius is medium: an AI agent misusing this could spam, impersonate the user, or post inappropriate content to a public audience, but the damage is not permanent (posts can be deleted) and does not involve financial transactions or destructive…
From the tool's definition Tool description states it 'Publishes a text-only post to Threads' and 'creates a container, then publishes it.' The return value is the 'Media ID of the published thread,' confirming a persistent write action.
Documented attack patterns abuse exactly the kind of access threads_publish_text gives an agent:
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_publish_text:
{
"version": "1",
"default": "deny",
"tools": {
"threads_publish_text": {
"limits": [
{
"counter": "threads_publish_text_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}threads_publish_text 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.
Free to start. No card required.
Publishes a text-only post to Threads. Two-step flow: creates a container, then publishes it. Args: - threads_user_id (string): Threads user ID - text (string): Post text (up to 500 characters) - reply_to_id (string, optional): Thread ID to reply to - quote_post_id (string, optional): Thread ID to quote Returns: Media ID of the published thread. 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.
Register the Meta MCP Server MCP server in PolicyLayer and add a rule for threads_publish_text: 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.
threads_publish_text 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 threads_publish_text 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 threads_publish_text. 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.
threads_publish_text 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.
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.
Free to start. No card required.
200 Meta MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.