Fetch the current marketing pixel IDs configured for a store: Meta (Facebook), TikTok, GA4, Google Ads.
AI agents call wafle_pixels_get to retrieve information from wafle 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 existing marketing pixel identifiers (Meta, TikTok, GA4, Google Ads) from a store's configuration. The verb 'Fetch' and the read-only nature of retrieving configuration data places it squarely in the Read category. There is no creation, modification, deletion, code execution, or financial transaction involved.
From the tool's definition Tool name 'wafle_pixels_get' and description 'Fetch the current marketing pixel IDs configured for a store' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Fetch the current marketing pixel IDs configured for a store: Meta (Facebook), TikTok, GA4, Google Ads. It is categorised as a Read tool in the wafle MCP server MCP Server, which means it retrieves data without modifying state.
Register the wafle MCP server MCP server in PolicyLayer and add a rule for wafle_pixels_get: 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 wafle MCP server. Nothing to install.
wafle_pixels_get 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 wafle_pixels_get 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 wafle_pixels_get. 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.
wafle_pixels_get is provided by the wafle MCP server MCP server (the33warehouse-tech/wafle-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 →