AI agents call list_campaigns to retrieve information from Flour Ads without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing campaign data without creating, modifying, deleting, or executing any actions. It is purely informational and read-only, making it the lowest risk category.
From the tool's definition Tool name 'list_campaigns' and description 'List all campaigns for an account' clearly indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List all campaigns for an account. It is categorised as a Read tool in the Flour Ads MCP Server, which means it retrieves data without modifying state.
Register the Flour Ads MCP server in PolicyLayer and add a rule for list_campaigns: 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 Flour Ads. Nothing to install.
list_campaigns is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_campaigns 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 list_campaigns. 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.
list_campaigns is provided by the Flour Ads MCP server (wayy-research/flour-ads). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →