Retrieves posts published on the Facebook Page
AI agents call get_page_posts to retrieve information from Facebook MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation that fetches existing posts from a Facebook Page. It does not create, modify, delete, or execute any actions—it only retrieves data. This is a standard Read category tool with low severity since unauthorized access to public or page-owned posts poses minimal security risk compared to destructive or financial operations.
From the tool's definition Tool name 'get_page_posts' and description 'Retrieves posts published on the Facebook Page' indicate a data retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_page_posts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Facebook MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_page_posts:
{
"version": "1",
"default": "deny",
"tools": {
"get_page_posts": {}
}
}get_page_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.
Retrieves posts published on the Facebook Page. It is categorised as a Read tool in the Facebook MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Facebook MCP Server MCP server in PolicyLayer and add a rule for get_page_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 Facebook MCP Server. Nothing to install.
get_page_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 get_page_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 get_page_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.
get_page_posts is provided by the Facebook MCP Server MCP server (tiroshanm/facebook-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Facebook MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 Facebook MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.