Submit a consultation request to the Default Privacy team. Requires explicit user consent (consent: true) and a contact email. Does NOT trigger formation — it queues a human follow-up. When to call: when the user's situation is ambiguous, multi-entity, or legally-sensitive (e.g. multi-state real-...
Part of the Default Privacy server.
Free to start. No card required.
AI agents may call request_consultation to permanently remove or destroy resources in Default Privacy. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call request_consultation in a loop, permanently destroying resources in Default Privacy. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"request_consultation"
]
}See the full Default Privacy policy for all 33 tools.
These attack patterns abuse exactly the kind of access request_consultation gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Submit a consultation request to the Default Privacy team. Requires explicit user consent (consent: true) and a contact email. Does NOT trigger formation — it queues a human follow-up. When to call: when the user's situation is ambiguous, multi-entity, or legally-sensitive (e.g. multi-state real-estate portfolio, public figure with active legal threat) and self-serve tools aren't enough. PREFER self-serve flows for straightforward formation. We do not file on the user's behalf without their explicit intake. Input Requirements: - email is REQUIRED. The user's contact email. - consent is REQUIRED and MUST be true. The tool refuses to submit otherwise. - message is OPTIONAL free-text from the user. - context is OPTIONAL free-text the agent can pass forward (prior diagnostic findings, jurisdiction interest). Output: { status: "submitted" | "queued" | "rate_limited", reference_id, expected_response_time, related_docs }. On rate-limit the tool returns a structured RATE_LIMITED error with a retry-after hint. PREFER quoting the expected_response_time so the user has a clear horizon. Never promise a specific outcome — consultations are exploratory.. It is categorised as a Destructive tool in the Default Privacy MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Default Privacy MCP server in PolicyLayer and add a rule for request_consultation: 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.
request_consultation is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the request_consultation 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 request_consultation. 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.
request_consultation 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.