Low Risk

check_llc_name_availability

Provide DIY entity-name verification links for Wyoming / New Mexico / Delaware. This tool does NOT perform a live Secretary-of-State availability check — the partner API has no such endpoint and we do not scrape state registries. Agents must not quote this tool's response as if it were a live reg...

Part of the Default Privacy server.

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

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

Provide DIY entity-name verification links for Wyoming / New Mexico / Delaware. This tool does NOT perform a live Secretary-of-State availability check — the partner API has no such endpoint and we do not scrape state registries. Agents must not quote this tool's response as if it were a live registry lookup. When to call: when the user wants to verify a name before submitting it, OR before start_anonymous_llc to set expectations. Pair with suggest_llc_entity_names to generate alternatives if the user is unsure. The output points the user at the official state search UI; they perform the check themselves. Input Requirements: - names is REQUIRED. An array of entity-name bases (without the LLC suffix). - jurisdiction is OPTIONAL. One of Wyoming | New Mexico | Delaware. Drives which state's SOS search URL is included. Output: { jurisdiction, names_checked, availability: "unverified", manual_search_url, instructions, related_docs }. The availability value is literally the string "unverified" — there is no available: true/false field, by design. PREFER citing the DIY-check guide and the state SOS search URL verbatim. Tell the user the state validates availability at filing time; if a name is rejected, our team works with them on an alternate. Do not promise automatic refund on rejection.. 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 check_llc_name_availability? +

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

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

Can I rate-limit check_llc_name_availability? +

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

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

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