Get events received by a pixel in the last 24 hours,
AI agents call get_pixel_events to retrieve information from KonQuest 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 historical event data from a Meta Ads pixel without modifying, deleting, or executing external actions. While classified as Read, severity is medium because pixel event data may contain user behavior tracking information, sensitive conversion data, or PII-adjacent insights that could be misused if an AI agent exfiltrates or misinterprets the data in context of campaign optimization.
From the tool's definition Tool name 'get_pixel_events' and description 'Get events received by a pixel in the last 24 hours' indicate data retrieval with no modification or deletion. The verb 'Get' and absence of side-effect language confirm this is a read operation.
Attacks that exploit this kind of access
Get events received by a pixel in the last 24 hours,. It is categorised as a Read tool in the KonQuest Meta Ads MCP MCP Server, which means it retrieves data without modifying state.
Register the KonQuest Meta Ads MCP server in PolicyLayer and add a rule for get_pixel_events: 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 KonQuest Meta Ads MCP. Nothing to install.
get_pixel_events 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_pixel_events 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_pixel_events. 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_pixel_events is provided by the KonQuest Meta Ads MCP server (brandu-mos/konquest-meta-ads-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 →