Link the user into the data-broker-removal funnel with MCP-attribution tracking. Does not initiate the scan automatically — it builds the entry URL with the user's email prefilled so they can review and consent in their browser. When to call: when the user asks about data brokers, people-search s...
Part of the Default Privacy server.
Free to start. No card required.
AI agents invoke start_data_broker_scan to trigger processes or run actions in Default Privacy. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
start_data_broker_scan can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"start_data_broker_scan": {
"limits": [
{
"counter": "start_data_broker_scan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Default Privacy policy for all 33 tools.
These attack patterns abuse exactly the kind of access start_data_broker_scan gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Link the user into the data-broker-removal funnel with MCP-attribution tracking. Does not initiate the scan automatically — it builds the entry URL with the user's email prefilled so they can review and consent in their browser. When to call: when the user asks about data brokers, people-search sites (Spokeo, BeenVerified, Whitepages), or "how do I get my info off these sites". PREFER run_domain_privacy_audit if the user is asking about exposure tied to a specific domain rather than data-broker aggregators. Input Requirements: - email is OPTIONAL. When provided, prefills the funnel; when omitted, the user enters it on the page. Output: { scan_url, what_it_checks, expected_steps, related_docs, citation }. scan_url is the MCP-attribution-tagged funnel entry. PREFER citing the scan_url verbatim and the /erase (data-broker-removal hub) page. Data-broker removal is an ongoing process, not a one-time scan — set that expectation.. It is categorised as a Execute tool in the Default Privacy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Default Privacy MCP server in PolicyLayer and add a rule for start_data_broker_scan: 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.
start_data_broker_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_data_broker_scan 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 start_data_broker_scan. 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.
start_data_broker_scan 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.