update_custom_audience · Meta Marketing API MCP Server MCP

WHAT IT DOES

What update_custom_audience does on Meta Marketing API MCP Server

AI agents use update_custom_audience to create or update resources in Meta Marketing API MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta Marketing API MCP Server environment.

WHY IT NEEDS A POLICY

Why update_custom_audience needs a policy

Updating custom audiences modifies targeting data reversibly—audiences can be adjusted or replaced without permanent loss. This is Write rather than Execute because it directly modifies a data resource (custom audience definition) rather than triggering code execution or external operations. It is not Destructive because audience updates are reversible.

From the tool's definition Tool name 'update_custom_audience' indicates modification of audience data. The server manages 'full campaign lifecycle management' and 'audience targeting,' and sibling tools include create operations (create_ad, create_ad_set, create_ad_creative),…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_custom_audience Rate-limited

update_custom_audience stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_custom_audience": {
      "limits": [
        {
          "counter": "update_custom_audience_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about update_custom_audience

What does the update_custom_audience tool do? +

update_custom_audience. It is categorised as a Write tool in the Meta Marketing API MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_custom_audience? +

Register the Meta Marketing API MCP Server MCP server in PolicyLayer and add a rule for update_custom_audience: 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 Meta Marketing API MCP Server. Nothing to install.

What risk level is update_custom_audience? +

update_custom_audience is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_custom_audience? +

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

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

update_custom_audience is provided by the Meta Marketing API MCP Server MCP server (pythonando/meta-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.