Get performance insights for campaigns, ad sets, or ads
AI agents call get_insights to retrieve information from Meta Marketing API 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 and queries performance metrics and analytics data from Meta's advertising platform. It has no side effects, does not modify data, execute code, delete records, or commit financial obligations. It is a straightforward read operation that queries existing campaign and ad performance information.
From the tool's definition Tool name is 'get_insights' and description states 'Get performance insights for campaigns, ad sets, or ads' - uses the verb 'Get' and describes retrieval of analytics/performance data with no mention of modifications, deletions, or financial transactions.
Attacks that exploit this kind of access
Get performance insights for campaigns, ad sets, or ads. It is categorised as a Read tool in the Meta Marketing API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Meta Marketing API MCP Server MCP server in PolicyLayer and add a rule for get_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 Marketing API MCP Server. Nothing to install.
get_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_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_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_insights is provided by the Meta Marketing API MCP Server MCP server (pythonando/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 →