AI agents call post_get to retrieve information from Meta 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 operation fetching a single post from the Meta Graph API. The HTTP GET method and read-only server description confirm no side effects or data modification occurs.
From the tool's definition GET /{post_id} — uses HTTP GET method to retrieve a single post by ID; server is described as 'Read-only MCP server'
Attacks that exploit this kind of access
GET /{post_id}. Post id format is usually. It is categorised as a Read tool in the Meta MCP Server, which means it retrieves data without modifying state.
Register the Meta MCP server in PolicyLayer and add a rule for post_get: 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. Nothing to install.
post_get 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 post_get 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 post_get. 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.
post_get is provided by the Meta MCP server (nourpups/meta-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →