This record as markdown: /tools/adbutler/list-audiences.md
What list_audiences does on AdButler
AI agents call list_audiences to retrieve information from AdButler without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Max results to return (default 100, max 100) |
offset | number | — | Pagination offset |
user_db_id | number | Yes | User database ID |
Parameters from the server's own tool schema.
Why list_audiences is rated Low
This tool retrieves audience data without modifying, executing operations, or destructing resources. However, it accesses user audience data which could contain sensitive information about marketing segments, user groups, or personal information, warranting medium severity if exposed to an unauthorized AI agent. The confidence is high because the description clearly indicates a read operation.
From the tool's definition Tool name 'list_audiences' and description 'List all audiences in a user database' indicate a query operation that retrieves data.
Attacks that exploit this kind of access
The rule that runs list_audiences safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AdButler, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_audiences, this is the rule to start with:
list_audiences is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every list_audiences call is checked against it from then on.
Questions about list_audiences
List all audiences in a user database. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
list_audiences accepts 3 parameters: limit, offset, user_db_id. Required: user_db_id. The full parameter table on this page comes from the server's own tool schema.
Register the AdButler MCP server in PolicyLayer and add a rule for list_audiences: 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 AdButler. Nothing to install.
list_audiences 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_audiences 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_audiences. 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_audiences is provided by the AdButler MCP server (adbutler/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AdButler, and thousands of servers like it.
This server
Across the catalogue