Fetch insights metrics for a Facebook Page (impressions, engaged users, fans, etc.). Provide either a date_preset OR a time_range.
AI agents call get_page_insights to retrieve information from Claude Meta without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves Facebook Page analytics data without creating, modifying, deleting, or executing any actions. It is a pure read operation with minimal security risk—the worst-case scenario is unauthorized viewing of public or semi-public metrics. No side effects, no resource consumption, no financial impact.
From the tool's definition Tool name 'get_page_insights' and description 'Fetch insights metrics' indicate data retrieval. Metrics listed (impressions, engaged users, fans) are analytics queries with no modification or execution.
Attacks that exploit this kind of access
Fetch insights metrics for a Facebook Page (impressions, engaged users, fans, etc.). Provide either a date_preset OR a time_range. It is categorised as a Read tool in the Claude Meta MCP Server, which means it retrieves data without modifying state.
Register the Claude Meta MCP server in PolicyLayer and add a rule for get_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 Claude Meta. Nothing to install.
get_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 get_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 get_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.
get_page_insights is provided by the Claude Meta MCP server (maxx3250/claude-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 →