Create a Threads media container using only officially documented publish parameters.
AI agents use create_thread_container 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 new media container objects within Threads, which is a Write operation—data is created and can be subsequently modified or removed. It does not execute arbitrary code, delete data irreversibly, move money, or trigger external side effects beyond container creation.
From the tool's definition Tool name 'create_thread_container' and description 'Create a Threads media container' indicate data creation.
Attacks that exploit this kind of access
Create a Threads media container using only officially documented publish parameters. 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_thread_container: 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_thread_container 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_thread_container 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_thread_container. 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_thread_container 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 →