AI agents call page_insights 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 retrieves page insights/analytics data without any capability to create, modify, delete, or execute external operations. GET requests that only query data with no side effects are classified as Read category. Severity is low because accessing analytics metadata about a page poses minimal risk compared to other categories.
From the tool's definition Tool description states 'GET /{page_id}/insights' which is an HTTP GET request for retrieving analytics data. Server is explicitly described as 'Read-only MCP server' with no capability to modify, delete, or execute operations.
Attacks that exploit this kind of access
GET /{page_id}/insights. Requires a Page Access Token (resolved automatically). 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 page_insights: 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.
page_insights 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 page_insights 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 page_insights. 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.
page_insights 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 →