meta_ads_conversions_send

THE RISK

High Risk

Why meta_ads_conversions_send needs a policy

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

Documented attack patterns abuse exactly the kind of access meta_ads_conversions_send gives an agent:

POLICY

How to control meta_ads_conversions_send

PolicyLayer is an MCP gateway — it sits between your AI agents and Mureo, and nothing reaches the server without passing your rules. This is the rule we recommend for meta_ads_conversions_send:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "meta_ads_conversions_send": {
      "limits": [
        {
          "counter": "meta_ads_conversions_send_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

Create a free account and register Mureo — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Mureo tools

Financial google_ads_budget_reallocation Propose a budget reallocation plan by cutting up to 20% Financial meta_ads_instagram_boost Boosts an organic Instagram post by creating a paid ad Financial meta_ads_page_posts_boost Boosts an existing Facebook Page post by creating a paid Destructive google_ads_callouts_remove Detach a callout asset from a Google Ads campaign by Destructive google_ads_conversions_remove Archive (status=REMOVED) a Google Ads conversion action. Destructive google_ads_keywords_remove Removes (soft-deletes) a single keyword criterion from an ad Destructive google_ads_negative_keywords_remove Removes a single campaign-level negative keyword. Returns the Destructive google_ads_sitelinks_remove Detach a sitelink asset from a Google Ads campaign by

All 185 Mureo tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Mureo → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

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.

Enforce policy on every Mureo tool call.

Start from Mureo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →