AI agents use create_budget_schedule to create or update resources in Meta Ads MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta Ads MCP environment.
This tool creates budget scheduling configuration for Meta ad campaigns, which is a reversible modification of campaign settings. While the description is empty (lowering confidence slightly), the name and server context clearly indicate data creation rather than retrieval (Read), code execution (Execute), permanent deletion (Destructive), or financial transactions (Financial).
From the tool's definition Tool name is 'create_budget_schedule' which indicates creation of a budget schedule for advertising campaigns. Given the server context of Meta Ads management, this creates advertising budget allocation/scheduling configuration.
Documented attack patterns abuse exactly the kind of access create_budget_schedule gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meta Ads MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create_budget_schedule:
{
"version": "1",
"default": "deny",
"tools": {
"create_budget_schedule": {
"limits": [
{
"counter": "create_budget_schedule_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_budget_schedule 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.
create_budget_schedule. It is categorised as a Write tool in the Meta Ads MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Meta Ads MCP server in PolicyLayer and add a rule for create_budget_schedule: 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 Ads MCP. Nothing to install.
create_budget_schedule 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 create_budget_schedule 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 create_budget_schedule. 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.
create_budget_schedule is provided by the Meta Ads MCP server (pipeboard-co/meta-ads-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 42 Meta Ads MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
42 Meta Ads MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.