get_campaign_performance
AI agents call get_campaign_performance 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 campaign performance data without modifying, deleting, or executing operations. It falls squarely into the Read category. While the tool description is empty, the name combined with the server's stated capability to provide 'performance analytics' and the 'get_' convention for read operations provides high confidence.
From the tool's definition Tool name 'get_campaign_performance' indicates retrieval of performance analytics data. Server description states it 'supports full campaign lifecycle management, performance analytics, audience targeting, and creative optimization.' The 'get_' prefix and…
Attacks that exploit this kind of access
get_campaign_performance. 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_campaign_performance: 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_campaign_performance 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_campaign_performance 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_campaign_performance. 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_campaign_performance 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 →