Fetch per-post insights (engagement, reach, impressions, saves) for a single IG media item.
AI agents call get_instagram_post_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 analytics data from Instagram without modifying, deleting, or executing any operations. It is a straightforward data query operation that returns performance metrics for a post, making it a Read category tool with low severity.
From the tool's definition The tool description explicitly states it 'Fetch[es] per-post insights' and enumerates read-only metrics: 'engagement, reach, impressions, saves'. The verb 'fetch' and the nature of the data (insights/analytics) indicate retrieval with no side effects.
Attacks that exploit this kind of access
Fetch per-post insights (engagement, reach, impressions, saves) for a single IG media item. 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_instagram_post_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_instagram_post_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_instagram_post_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_instagram_post_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_instagram_post_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 →