Creates a new post on a Facebook Page. Requires: meta_list_pages must be called first to load page tokens. Args: - page_id (string): Facebook Page ID to post to - message (string): Text content of the post - link (string, optional): URL to attach to the post (creates a link preview) - published (...
AI agents use meta_create_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 tool creates or modifies data reversibly (Write category) rather than executing arbitrary code (Execute) or deleting data (Destructive). The severity is medium because misuse could result in unauthorized posting of content, misinformation, or spam to a Facebook Page reaching potentially large audiences, but the impact is reversible through post deletion.
From the tool's definition Tool description explicitly states 'Creates a new post on a Facebook Page' with parameters for message content, link attachment, and publish timing.
Documented attack patterns abuse exactly the kind of access meta_create_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_create_post:
{
"version": "1",
"default": "deny",
"tools": {
"meta_create_post": {
"limits": [
{
"counter": "meta_create_post_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}meta_create_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.
Creates a new post on a Facebook Page. Requires: meta_list_pages must be called first to load page tokens. Args: - page_id (string): Facebook Page ID to post to - message (string): Text content of the post - link (string, optional): URL to attach to the post (creates a link preview) - published (boolean, optional): If false, saves as draft. Default true. - scheduled_publish_time (number, optional): Unix timestamp for scheduling (must be 10 min to 30 days in future; published must be false) Returns: Post ID of the created post. Notes: - Maximum post length: ~63,206 characters - Scheduling requires the page to have Page Publishing Authorization. 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_create_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_create_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_create_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_create_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_create_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.