Sends a server-side conversion event to Meta via the Conversions API. Args: - pixel_id: Meta Pixel ID - event_name: Standard events: Purchase, Lead, AddToCart, CompleteRegistration, ViewContent, Search, InitiateCheckout, AddPaymentInfo, AddToWishlist, Subscribe, StartTrial, Contact, CustomizeProd...
AI agents invoke meta_send_conversion_event to trigger actions in Meta MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation by sending conversion event data to Meta's Conversions API. It doesn't just read or write local data — it fires a real-time signal to an external ad platform that can influence ad optimization, attribution, and billing (e.g., a 'Purchase' event can trigger downstream ad spend adjustments).
From the tool's definition Sends a server-side conversion event to Meta via the Conversions API
Documented attack patterns abuse exactly the kind of access meta_send_conversion_event 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_send_conversion_event:
{
"version": "1",
"default": "deny",
"tools": {
"meta_send_conversion_event": {
"limits": [
{
"counter": "meta_send_conversion_event_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}meta_send_conversion_event stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Sends a server-side conversion event to Meta via the Conversions API. Args: - pixel_id: Meta Pixel ID - event_name: Standard events: Purchase, Lead, AddToCart, CompleteRegistration, ViewContent, Search, InitiateCheckout, AddPaymentInfo, AddToWishlist, Subscribe, StartTrial, Contact, CustomizeProduct, Donate, FindLocation, Schedule, SubmitApplication, PageView. Custom event names also accepted. - event_time: Unix timestamp - event_source_url (optional): URL where conversion happened - user_data: At minimum one of: em (hashed email), ph (hashed phone), fbc, fbp, client_ip_address, client_user_agent, external_id - custom_data (optional): { currency, value, content_name, content_ids, content_type, order_id, num_items } - event_id (optional): For deduplication with browser pixel - action_source:. It is categorised as a Execute tool in the Meta MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Meta MCP Server MCP server in PolicyLayer and add a rule for meta_send_conversion_event: 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_send_conversion_event is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the meta_send_conversion_event 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_send_conversion_event. 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_send_conversion_event 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.