Create a Threads container and then publish it, returning both IDs.
AI agents use create_and_publish_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 the Threads platform, modifying the platform's data state. It is a Write action because it creates/posts content reversibly. Severity is medium because misuse could result in spam, misinformation, or unwanted posts at scale, but the blast radius is limited to content publication rather than data destruction or financial impact.
From the tool's definition Tool description states 'Create a Threads container and then publish it' — explicit write operations that create new content.
Attacks that exploit this kind of access
Create a Threads container and then publish it, returning both IDs. 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 create_and_publish_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.
create_and_publish_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 create_and_publish_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 create_and_publish_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.
create_and_publish_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 →