Publishes a pre-created Instagram media container. Use after checking container status is FINISHED. Useful for reels/videos where container creation and publishing are done in separate steps. Args: - ig_account_id (string): Instagram account ID - container_id (string): Container ID (from a previo...
AI agents use meta_publish_instagram_container 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 or modifies data reversibly by publishing content to Instagram. While publishing is a significant action with broad audience reach, it is not destructive (the content can be deleted afterward), not financial, and not arbitrary code execution. The high severity reflects the blast radius: an AI agent could publish unauthorized, offensive, or brand-damaging content to a potentially large follower base.
From the tool's definition Tool description explicitly states it 'Publishes a pre-created Instagram media container' — a direct modification action that creates public content on Instagram. The tool modifies the state of the account by publishing media to a live social platform.
Documented attack patterns abuse exactly the kind of access meta_publish_instagram_container 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 meta_publish_instagram_container:
{
"version": "1",
"default": "deny",
"tools": {
"meta_publish_instagram_container": {
"limits": [
{
"counter": "meta_publish_instagram_container_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}meta_publish_instagram_container 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 pre-created Instagram media container. Use after checking container status is FINISHED. Useful for reels/videos where container creation and publishing are done in separate steps. Args: - ig_account_id (string): Instagram account ID - container_id (string): Container ID (from a previous create step). 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 meta_publish_instagram_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 Meta MCP Server. Nothing to install.
meta_publish_instagram_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 meta_publish_instagram_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 meta_publish_instagram_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.
meta_publish_instagram_container 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.