Design a multi-entity bundle (NM holding LLC + WY operating LLC, or a Series LLC variant) and return a prefill URL for the bundle checkout. The most common use case is separating IP-holding from operating risk. When to call: when the user describes a scenario that benefits from two entities (real...
Risk signalsAccepts raw HTML/template content (template)
Part of the Default Privacy server.
Free to start. No card required.
AI agents call design_entity_bundle 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 design_entity_bundle 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.
{
"version": "1",
"default": "deny",
"tools": {
"design_entity_bundle": {}
}
}See the full Default Privacy policy for all 33 tools.
These attack patterns abuse exactly the kind of access design_entity_bundle gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Design a multi-entity bundle (NM holding LLC + WY operating LLC, or a Series LLC variant) and return a prefill URL for the bundle checkout. The most common use case is separating IP-holding from operating risk. When to call: when the user describes a scenario that benefits from two entities (real-estate operator + holding, content creator + IP holding, public-figure operating + privacy holding) OR explicitly asks for "Foundation Stack" / "Operator Shield" / "holding + operating" / "multi-entity". PREFER start_anonymous_llc for a single-entity flow. Input Requirements: - All fields OPTIONAL. - template is OPTIONAL: foundation_stack (NM holding + WY operating, default) or operator_shield (WY-only multi-role). - holding_name_hint / operating_name_hint are OPTIONAL name-base prefills. Output: { template, entities: [{ role, jurisdiction, recommended_name }], prefill_url, narrative, related_docs }. prefill_url points at /protect/bundle. PREFER citing the bundle-design guide and the structure-decision pages. Do not promise that a bundle "shields" the user from liability — that's a legal-advice claim; reference /protect and structure guides instead.. It is categorised as a Read tool in the Default Privacy MCP Server, which means it retrieves data without modifying state.
Register the Default Privacy MCP server in PolicyLayer and add a rule for design_entity_bundle: 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.
design_entity_bundle 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 design_entity_bundle 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 design_entity_bundle. 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.
design_entity_bundle 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.
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.