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

meta_ads_conversions_send

Sends a batch of arbitrary conversion events to the Meta

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.md

What meta_ads_conversions_send does on Mureo

AI agents invoke meta_ads_conversions_send 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 is rated High

This tool triggers external operations by sending conversion event data to Meta's platform. It doesn't merely read or write local data — it fires server-side events to an external advertising system, which can affect attribution, billing, audience building, and ad optimization.

From the tool's definition Sends a batch of arbitrary conversion events to the Meta

Questions about meta_ads_conversions_send

What does the meta_ads_conversions_send tool do? +

Sends a batch of arbitrary conversion events to the Meta. 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? +

Register the Mureo MCP server in PolicyLayer and add a rule for meta_ads_conversions_send: 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? +

meta_ads_conversions_send 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? +

Yes. Add a rate_limit block to the meta_ads_conversions_send 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 completely? +

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

meta_ads_conversions_send 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.