Gets performance insights for an Instagram professional account. Args: - ig_account_id (string): Instagram account ID - metrics (string[]): Metrics to retrieve. Options: Interactions: accounts_engaged, total_interactions, likes, comments, shares, saves, replies, reposts, reach, views, profile_lin...
AI agents call meta_get_instagram_account_insights to retrieve information from Meta MCP Server 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 about an Instagram account's performance without creating, modifying, deleting, or triggering external operations. The metrics available are all read-only account performance indicators. Even with account access, misuse would at worst expose performance data already visible to the account owner or authorized analytics viewers, making it low severity.
From the tool's definition Tool description states it 'Gets performance insights' and lists only retrieval-focused metrics (accounts_engaged, interactions, likes, comments, reach, views, demographics, etc.). No modification, creation, deletion, or external execution occurs.
Documented attack patterns abuse exactly the kind of access meta_get_instagram_account_insights gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meta MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for meta_get_instagram_account_insights:
{
"version": "1",
"default": "deny",
"tools": {
"meta_get_instagram_account_insights": {}
}
}meta_get_instagram_account_insights 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.
Gets performance insights for an Instagram professional account. Args: - ig_account_id (string): Instagram account ID - metrics (string[]): Metrics to retrieve. Options: Interactions: accounts_engaged, total_interactions, likes, comments, shares, saves, replies, reposts, reach, views, profile_links_taps, account_repost_count Legacy: impressions (deprecated v22.0+), follower_count, email_contacts, phone_call_clicks, text_message_clicks, get_directions_clicks, profile_views, website_clicks Demographics: engaged_audience_demographics, reached_audience_demographics, follower_demographics, online_followers Note: account_repost_count (Dec 2025) returns the total number of reposts across the account for the given period. - period (string):. It is categorised as a Read tool in the Meta MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Meta MCP Server MCP server in PolicyLayer and add a rule for meta_get_instagram_account_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 MCP Server. Nothing to install.
meta_get_instagram_account_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 meta_get_instagram_account_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 meta_get_instagram_account_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.
meta_get_instagram_account_insights is provided by the Meta MCP Server MCP server (oliverames/meta-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Meta MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
200 Meta MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.