Low Risk

list_audiences

List every audience-specific privacy guide Default Privacy publishes — currently 22 (doctors, accountants, realtors, content creators, high-net-worth individuals, OnlyFans creators, etc.). Each entry returns a slug, audience label, one-line headline, intent ("business" | "asset" | "emergency"), a...

Part of the Default Privacy server.

list_audiences is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE DEFAULT PRIVACY →

Free to start. No card required.

AI agents call list_audiences to retrieve information from Default Privacy without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though list_audiences only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_audiences": {}
  }
}

See the full Default Privacy policy for all 33 tools.

Get this rule live on your own Default Privacy server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY DEFAULT PRIVACY →

View all 33 tools →

These attack patterns abuse exactly the kind of access list_audiences gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so list_audiences only ever does what you allow.

SECURE DEFAULT PRIVACY →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the list_audiences tool do? +

List every audience-specific privacy guide Default Privacy publishes — currently 22 (doctors, accountants, realtors, content creators, high-net-worth individuals, OnlyFans creators, etc.). Each entry returns a slug, audience label, one-line headline, intent ("business" | "asset" | "emergency"), and the recommended LLC structure shape ("single" | "bundle") + state. Call get_audience next for the full FAQ + risks + structure rationale on a chosen slug. When to call: when the user describes their profession or situation ("I'm a doctor", "real estate agent", "OnlyFans creator", "I have a lot of assets") and you want to find a matching audience-specific guide. Also call when the user asks "what kinds of clients do you serve" or "who uses this". PREFER get_audience directly when the user has already named a specific audience slug. Input Requirements: none. Output: { audiences: [{ slug, audience, headline, intent, structureType, state }], total, citation }. The list is sorted by slug. structureType is "single" for one-LLC recommendations and "bundle" for multi-entity stacks (typically high-net-worth or heavy asset-protection scenarios). PREFER quoting the matching audience's headline to the user and then chaining get_audience(slug) to retrieve the full guidance before recommending a structure.. It is categorised as a Read tool in the Default Privacy MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_audiences? +

Register the Default Privacy 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 Default Privacy. Nothing to install.

What risk level is list_audiences? +

list_audiences is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_audiences? +

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.

How do I block list_audiences completely? +

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.

What MCP server provides list_audiences? +

list_audiences is provided by the Default Privacy MCP server (https://defaultprivacy.com/api/privacy/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Default Privacy tool call.

Deterministic rules across all 33 Default Privacy tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.