meta.passthrough.write · Ads MCP: Risk & Policy

WHAT IT DOES

What meta.passthrough.write does on Ads

AI agents invoke meta.passthrough.write to trigger actions in Ads. 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 IT NEEDS A POLICY

Why meta.passthrough.write needs a policy

This tool is a generic passthrough that can execute arbitrary POST or DELETE requests against the Meta Graph API. While it defaults to dry-run, when confirm_passthrough=true is set it can perform any operation including creating, modifying, or deleting campaigns, ads, audiences, and spend configurations.

From the tool's definition POST/DELETE any Meta Graph API endpoint... Requires confirm_passthrough=true. Dry-run by default. Logged.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

meta.passthrough.write Rate-limited

meta.passthrough.write 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "meta.passthrough.write": {
      "limits": [
        {
          "counter": "meta.passthrough.write_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ads, so you can run agents against it safely.

FAQ

Questions about meta.passthrough.write

What does the meta.passthrough.write tool do? +

Fallback: POST/DELETE any Meta Graph API endpoint. Use only when no named tool exists. Prefer meta.campaigns.create/pause/resume/update_budget, meta.adsets.pause/resume/update_budget, meta.ads.pause/resume. Requires confirm_passthrough=true. Dry-run by default. Logged. It is categorised as a Execute tool in the Ads 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.passthrough.write? +

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

What risk level is meta.passthrough.write? +

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

Can I rate-limit meta.passthrough.write? +

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

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

meta.passthrough.write is provided by the Ads MCP server (manlikemuneeb/ads-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.