Low Risk

get_audience

Fetch the full audience guide for one slug — the same content rendered on https://defaultprivacy.com/for/<slug>. Returns the audience's risks (with rationale), recommended LLC structure (type + state + why + suggested addons), deliverables, FAQs, and curated related links. The response is brand-v...

Part of the Default Privacy server.

get_audience 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 get_audience 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 get_audience 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": {
    "get_audience": {}
  }
}

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 get_audience 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 get_audience 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 get_audience tool do? +

Fetch the full audience guide for one slug — the same content rendered on https://defaultprivacy.com/for/<slug>. Returns the audience's risks (with rationale), recommended LLC structure (type + state + why + suggested addons), deliverables, FAQs, and curated related links. The response is brand-voice-clean and safe to quote to the user. When to call: after list_audiences when the user has chosen a specific audience, OR directly when the user names a profession that matches a known slug (use list_audiences first if you're unsure whether the slug exists). PREFER run_privacy_architecture_assessment when the user's situation spans multiple audiences or has unusual constraints. Input Requirements: - slug is REQUIRED. The audience slug as returned by list_audiences (e.g. doctors, accountants, high-net-worth). The tool lowercases + trims internally. Output: { audience: { slug, audience, headline, subheadline, intent, risks, structure, deliverables, faqs, relatedLinks }, citation }. risks[].icon is the Lucide icon identifier name as a string — agents can ignore it; it's preserved for symmetry with the rendered page. PREFER quoting the citation URL (the audience's live page) and one or two FAQs that match the user's stated concern. On unknown slugs the tool throws a structured INVALID_INPUT error with the full list of known slugs in the hint, so the agent can recover by re-prompting or calling list_audiences.. 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 get_audience? +

Register the Default Privacy MCP server in PolicyLayer and add a rule for get_audience: 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 get_audience? +

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

Can I rate-limit get_audience? +

Yes. Add a rate_limit block to the get_audience 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 get_audience completely? +

Set action: deny in the PolicyLayer policy for get_audience. 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 get_audience? +

get_audience 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.