meta_ads_conversions_send_purchase
Sends a single Purchase event via the Meta Conversions API —
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
Attacks that exploit this kind of access
The rule that runs meta_ads_conversions_send_purchase safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mureo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For meta_ads_conversions_send_purchase, this is the rule to start with:
meta_ads_conversions_send_purchase 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mureo, apply this rule, and every meta_ads_conversions_send_purchase call is checked against it from then on.
Questions about meta_ads_conversions_send_purchase
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.
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.
meta_ads_conversions_send_purchase 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_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.
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.
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.
Across the catalogue