// SCAN REPORT

Flour Ads

8 tools. 4 can modify or destroy data without limits.

4 write tools that can modify data. Rate limits recommended.

Last updated: 2 Jul 2026

4 can modify or destroy data

4 read-only

8 tools total

Community server · catalogue entry verified 02/07/2026

How to control Flour Ads ↓

TOOL MAP

What Flour Ads exposes to your agents

Read (4) Write / Execute (4) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Flour Ads tools

Write · High create_campaign create_campaign creates new advertising campaigns, which is a reversible modification operation. Write · Medium resume_campaign The tool modifies existing data (campaign state) reversibly by reactivating a paused campaign. Write · High update_budget This tool modifies an existing campaign's budget parameter, which is a reversible write operation. Write · High pause_campaign Pausing a campaign is a reversible state change (it can be resumed via resume_campaign), making it Write rather than Destructive.

4 of Flour Ads's 8 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Flour Ads

PolicyLayer is an MCP gateway — it sits between your AI agents and Flour Ads, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "create_campaign": {
    "limits": [
      {
        "counter": "create_campaign_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "authenticate": {
    "limits": [
      {
        "counter": "authenticate_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Flour Ads — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON FLOUR ADS →

Instant setup, no code required.

FULL CATALOGUE

All 8 Flour Ads tools

WRITE 4 tools

Write create_campaign create_campaign Write pause_campaign Pause an active campaign. Write resume_campaign Resume a paused campaign. Write update_budget Update the daily budget for a campaign.

READ 4 tools

Read authenticate authenticate Read get_performance get_performance Read list_campaigns List all campaigns for an account. Read list_platforms List all available ad platforms.

FAQ

Questions about Flour Ads

How do I prevent bulk modifications through Flour Ads? +

The Flour Ads server has 4 write tools including create_campaign, pause_campaign, resume_campaign. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Flour Ads.

How many tools does the Flour Ads MCP server expose? +

8 tools across 2 categories: Read, Write. 4 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on Flour Ads? +

Register the Flour Ads MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Flour Ads tool call.

Deterministic rules across all 8 Flour Ads tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON FLOUR ADS →

Instant setup, no code required.

8 Flour Ads tools catalogued and risk-classified — across an index of 43,000+ MCP servers.