Creates an automated rule for managing ads, ad sets, or campaigns. Args: - ad_account_id (string): Ad account ID - name (string): Rule name - evaluation_spec (object): Conditions that trigger the rule (e.g., {
AI agents use meta_create_ad_rule to create or update resources in Meta MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta MCP Server environment.
This tool creates (write action) new automated rules within Meta's ad platform. While reversible (rules can be deleted/modified), it has high severity because misconfigured rules could cause unintended ad spend, targeting changes, or campaign modifications affecting financial outcomes. However, it does not directly commit money or delete data, so it is Write rather than Financial or Destructive.
From the tool's definition Tool name 'meta_create_ad_rule' and description 'Creates an automated rule for managing ads, ad sets, or campaigns' indicate a write operation that creates new configuration entities.
Documented attack patterns abuse exactly the kind of access meta_create_ad_rule gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meta MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for meta_create_ad_rule:
{
"version": "1",
"default": "deny",
"tools": {
"meta_create_ad_rule": {
"limits": [
{
"counter": "meta_create_ad_rule_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} meta_create_ad_rule 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.
Free to start. No card required.
Creates an automated rule for managing ads, ad sets, or campaigns. Args: - ad_account_id (string): Ad account ID - name (string): Rule name - evaluation_spec (object): Conditions that trigger the rule (e.g., {. It is categorised as a Write tool in the Meta MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Meta MCP Server MCP server in PolicyLayer and add a rule for meta_create_ad_rule: 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 MCP Server. Nothing to install.
meta_create_ad_rule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the meta_create_ad_rule 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_create_ad_rule. 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_create_ad_rule is provided by the Meta MCP Server MCP server (oliverames/meta-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Meta MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
200 Meta MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.