New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

meta_ads_conversions_send_purchase

Sends a single Purchase event via the Meta Conversions API —

SERVERMureo SOURCElogly/mureo
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/logly-mureo/meta-ads-conversions-send-purchase.md

What meta_ads_conversions_send_purchase does on Mureo

AI agents invoke meta_ads_conversions_send_purchase to trigger actions in Mureo. 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.

Why meta_ads_conversions_send_purchase is rated High

This tool triggers an external API call to Meta's Conversions API to register a Purchase event. While it doesn't directly move money, it sends conversion tracking data that affects ad bidding, attribution, and campaign optimization — and can influence financial spend indirectly. The primary action is 'sends' an event to an external system, making it Execute.

From the tool's definition Sends a single Purchase event via the Meta Conversions API

Questions about meta_ads_conversions_send_purchase

What does the meta_ads_conversions_send_purchase tool do? +

Sends a single Purchase event via the Meta Conversions API —. It is categorised as a Execute tool in the Mureo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on meta_ads_conversions_send_purchase? +

Register the Mureo MCP server in PolicyLayer and add a rule for meta_ads_conversions_send_purchase: 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 Mureo. Nothing to install.

What risk level is meta_ads_conversions_send_purchase? +

meta_ads_conversions_send_purchase is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit meta_ads_conversions_send_purchase? +

Yes. Add a rate_limit block to the meta_ads_conversions_send_purchase 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.

How do I block meta_ads_conversions_send_purchase completely? +

Set action: deny in the PolicyLayer policy for meta_ads_conversions_send_purchase. 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.

What MCP server provides meta_ads_conversions_send_purchase? +

meta_ads_conversions_send_purchase is provided by the Mureo MCP server (logly/mureo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Mureo, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mureo's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.