list_custom_audiences
AI agents call list_custom_audiences to retrieve information from KonQuest Meta Ads MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
List operations are non-destructive queries that retrieve existing data. Even though the description is uninformative, the verb 'list' clearly indicates a read action. The context of a Meta Ads management system where listing audiences is a routine diagnostic and operational task supports this classification.
From the tool's definition Tool name 'list_custom_audiences' contains 'list', a standard read operation verb. The empty description prevents direct confirmation of scope, but the naming convention and presence among campaign management tools suggests it retrieves audience data without…
Attacks that exploit this kind of access
list_custom_audiences. It is categorised as a Read tool in the KonQuest Meta Ads MCP MCP Server, which means it retrieves data without modifying state.
Register the KonQuest Meta Ads MCP server in PolicyLayer and add a rule for list_custom_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 KonQuest Meta Ads MCP. Nothing to install.
list_custom_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_custom_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_custom_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_custom_audiences is provided by the KonQuest Meta Ads MCP server (brandu-mos/konquest-meta-ads-mcp). 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 →