Create a repost container for a published Threads post and publish it immediately.
AI agents use repost_thread to create or update resources in Threads MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Threads MCP Server environment.
This tool creates and publishes new content on behalf of the user, which is a Write operation as it creates data reversibly. While republishing content could have reputational implications, it does not meet Destructive criteria (not irreversible) or Execute criteria (not arbitrary code execution).
From the tool's definition The tool description states 'Create a repost container for a published Threads post and publish it immediately.' The verbs 'Create' and 'publish' indicate the tool modifies data by creating new content (a repost) on the Threads platform.
Attacks that exploit this kind of access
Create a repost container for a published Threads post and publish it immediately. It is categorised as a Write tool in the Threads MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Threads MCP Server MCP server in PolicyLayer and add a rule for repost_thread: 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 Threads MCP Server. Nothing to install.
repost_thread 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 repost_thread 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 repost_thread. 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.
repost_thread is provided by the Threads MCP Server MCP server (poisonstefani-dev/threads-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 →