Publishes the same content to both a Facebook Page and Instagram simultaneously. Requires: meta_list_pages must be called first to load page tokens. Args: - page_id (string): Facebook Page ID - ig_account_id (string): Instagram professional account ID - message (string): Text content (used as FB ...
AI agents use meta_cross_post 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 is a Write operation because it creates and publishes new content to social media platforms, which is reversible (posts can be deleted). However, severity is high rather than medium because publishing to live accounts has significant reputational and engagement consequences: a compromised AI agent could rapidly post spam, misinformation, or inappropriate content across two major platforms and their audiences,…
From the tool's definition Tool 'publishes the same content to both a Facebook Page and Instagram simultaneously' and 'creates photo posts on both platforms' and 'creates Reels on both platforms' — the tool modifies user-facing content on live social media accounts by creating posts…
Documented attack patterns abuse exactly the kind of access meta_cross_post 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_cross_post:
{
"version": "1",
"default": "deny",
"tools": {
"meta_cross_post": {
"limits": [
{
"counter": "meta_cross_post_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} meta_cross_post 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 the same content to both a Facebook Page and Instagram simultaneously. Requires: meta_list_pages must be called first to load page tokens. Args: - page_id (string): Facebook Page ID - ig_account_id (string): Instagram professional account ID - message (string): Text content (used as FB post text and IG caption) - image_url (string, optional): Public image URL — creates photo posts on both platforms - video_url (string, optional): Public video URL — creates Reels on both platforms Logic: - If image_url: FB photo post + IG photo post (parallel) - If video_url: FB Reel + IG Reel (parallel) - If text only: FB text post only (IG doesn. 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_cross_post: 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_cross_post 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_cross_post 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_cross_post. 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_cross_post 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.