Lists posts from a Facebook Page feed. Requires: meta_list_pages called first to load page tokens. Args: - page_id (string): Facebook Page ID - limit (number): Max posts to return (1–100, default 20) - after (string, optional): Cursor for next page of results Returns: List of posts with message, ...
AI agents call meta_get_posts 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 and queries existing data from a Facebook Page feed without creating, modifying, deleting, or executing any external operations. It returns post metadata (message, permalink, created time, post ID) with pagination support via cursor. The only parameters are page_id, limit, and an optional cursor for pagination—all read-only query parameters.
From the tool's definition Tool name is 'meta_get_posts' and description states it 'Lists posts from a Facebook Page feed', which is a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access meta_get_posts 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_get_posts:
{
"version": "1",
"default": "deny",
"tools": {
"meta_get_posts": {}
}
}meta_get_posts 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.
Lists posts from a Facebook Page feed. Requires: meta_list_pages called first to load page tokens. Args: - page_id (string): Facebook Page ID - limit (number): Max posts to return (1–100, default 20) - after (string, optional): Cursor for next page of results Returns: List of posts with message, permalink, created time, and post ID. 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_get_posts: 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_get_posts 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_get_posts 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_get_posts. 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_get_posts 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.