Generate comprehensive Meta Ads performance reports. This is a premium feature available with Pipeboard Pro. Args: account_id: Meta Ads account ID (format: act_XXXXXXXXX) access_token: Meta API access token (optional - will use cached token if not provided) report_type: Type of report to generate...
AI agents call generate_report to retrieve information from Meta Ads MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and aggregates performance data from Meta Ads. It reads metrics and generates reports without creating, modifying, or deleting any data. The parameters (account_id, report_type, time_range, campaign_ids) are all for filtering/querying existing data. Severity is low as it only reads advertising performance data, though it could expose sensitive business metrics.
From the tool's definition Generate comprehensive Meta Ads performance reports
Documented attack patterns abuse exactly the kind of access generate_report gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meta Ads MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for generate_report:
{
"version": "1",
"default": "deny",
"tools": {
"generate_report": {}
}
}generate_report 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.
Generate comprehensive Meta Ads performance reports. This is a premium feature available with Pipeboard Pro. Args: account_id: Meta Ads account ID (format: act_XXXXXXXXX) access_token: Meta API access token (optional - will use cached token if not provided) report_type: Type of report to generate (account, campaign, comparison) time_range: Time period for the report (e.g., 'last_30d', 'last_7d', 'this_month') campaign_ids: Specific campaign IDs (required for campaign/comparison reports) export_format: Output format for the report (pdf, json, html) report_name: Custom name for the report (auto-generated if not provided) include_sections: Specific sections to include in the report breakdowns: Audience breakdown dimensions (age, gender, country, etc.) comparison_period: Time period for comparison analysis. It is categorised as a Read tool in the Meta Ads MCP MCP Server, which means it retrieves data without modifying state.
Register the Meta Ads MCP server in PolicyLayer and add a rule for generate_report: 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 Ads MCP. Nothing to install.
generate_report 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 generate_report 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 generate_report. 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.
generate_report is provided by the Meta Ads MCP server (pipeboard-co/meta-ads-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 42 Meta Ads MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
42 Meta Ads MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.