AI agents call get_post_comments 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 only queries and retrieves existing comment data without modifying, deleting, executing external operations, or creating financial obligations. It is a straightforward read operation on Facebook post comments.
From the tool's definition Tool name is 'get_post_comments' and description states it 'Retrieves comments for a specific post' — a pure data retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_post_comments 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_post_comments:
{
"version": "1",
"default": "deny",
"tools": {
"get_post_comments": {}
}
}get_post_comments 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 comments for a specific post. 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_post_comments: 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_post_comments 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_post_comments 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_post_comments. 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_post_comments 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.