Gets event volume stats for a pixel (critical for verifying pixel is firing). Args: - pixel_id (string): Pixel ID - start_time (string, optional): ISO date for start of range - end_time (string, optional): ISO date for end of range - aggregation (string, optional):
AI agents call meta_get_pixel_stats 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 queries and retrieves analytics data (pixel event statistics) without creating, modifying, deleting, or executing operations. It has minimal blast radius as misuse would only expose aggregated analytics visibility within the caller's authorized pixel scope, not financial transactions, destructive actions, or code execution.
From the tool's definition Tool description states 'Gets event volume stats for a pixel' — a retrieval operation with no modification capability. The arguments (pixel_id, start_time, end_time, aggregation) are all read filters; no destructive or write parameters are present.
Documented attack patterns abuse exactly the kind of access meta_get_pixel_stats 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_pixel_stats:
{
"version": "1",
"default": "deny",
"tools": {
"meta_get_pixel_stats": {}
}
} meta_get_pixel_stats 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 event volume stats for a pixel (critical for verifying pixel is firing). Args: - pixel_id (string): Pixel ID - start_time (string, optional): ISO date for start of range - end_time (string, optional): ISO date for end of range - aggregation (string, optional):. 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_pixel_stats: 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_pixel_stats 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_pixel_stats 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_pixel_stats. 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_pixel_stats 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.