Checks the publishing status of an Instagram media container (used for reels/videos that need processing). Args: - container_id (string): Container ID from a publish step Returns: status_code — IN_PROGRESS, FINISHED, ERROR, EXPIRED.
AI agents call meta_check_instagram_container to retrieve information from Meta MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about a media container's processing status without side effects. It is a pure read operation that does not create, modify, delete, or execute any actions. The low severity reflects minimal blast radius if misused by an AI agent—at worst, repeated status checks could cause minor resource overhead.
From the tool's definition Tool description states it 'Checks the publishing status' and returns status codes (IN_PROGRESS, FINISHED, ERROR, EXPIRED). No modification, deletion, or execution of external operations occurs—it only queries the state of an existing container.
Documented attack patterns abuse exactly the kind of access meta_check_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_check_instagram_container:
{
"version": "1",
"default": "deny",
"tools": {
"meta_check_instagram_container": {}
}
}meta_check_instagram_container is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Checks the publishing status of an Instagram media container (used for reels/videos that need processing). Args: - container_id (string): Container ID from a publish step Returns: status_code — IN_PROGRESS, FINISHED, ERROR, EXPIRED. It is categorised as a Read tool in the Meta MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Meta MCP Server MCP server in PolicyLayer and add a rule for meta_check_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_check_instagram_container is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the meta_check_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_check_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_check_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.