Critical Risk →

preferences

Manage user preferences and memory settings. Actions: - get: Check if memory is enabled and retrieve saved preferences. Default action if not specified. - set: Save preferences. Requires explicit user consent before enabling memory. memory_enabled must be true before any other preferences, monito...

Risk signalsBulk/mass operation — affects multiple targets

Part of the DomainKits server.

preferences can permanently delete data in DomainKits, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE DOMAINKITS →

Free to start. No card required.

AI agents may call preferences to permanently remove or destroy resources in DomainKits. 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 preferences in a loop, permanently destroying resources in DomainKits. 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "preferences"
  ]
}

See the full DomainKits policy for all 38 tools.

Get this rule live on your own DomainKits server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY DOMAINKITS →

View all 38 tools →

These attack patterns abuse exactly the kind of access preferences 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 preferences only ever does what you allow.

SECURE DOMAINKITS →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the preferences tool do? +

Manage user preferences and memory settings. Actions: - get: Check if memory is enabled and retrieve saved preferences. Default action if not specified. - set: Save preferences. Requires explicit user consent before enabling memory. memory_enabled must be true before any other preferences, monitors, or strategies can be saved. - delete: Delete all stored user data permanently (preferences, monitors, strategies). GDPR Article 17: Right to erasure. All user data is encrypted at rest using AES-256-GCM and stored in isolated user directories. No one — including DomainKits staff — can read your data. Fully GDPR compliant. When action=get: - If reason="not_configured", ask the user with a clear choice: "I can remember your preferences, monitoring tasks, and discovery strategies across sessions. All data is encrypted. Would you like to enable this?" Only call with action=set and memory_enabled=true after explicit user consent. - MONITOR HANDLING: If monitors_count > 0, check monitors_summary. If can_check_count > 0, call get_monitors to auto-check domains. If can_check_count == 0, all monitors are in cooldown — inform the user when next check is available (next_check field), do NOT call get_monitors. The domains list lets you answer "what am I monitoring?" without triggering a check. - If strategies_count > 0, proceed to call get_strategies.. It is categorised as a Destructive tool in the DomainKits MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on preferences? +

Register the DomainKits MCP server in PolicyLayer and add a rule for preferences: 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 DomainKits. Nothing to install.

What risk level is preferences? +

preferences is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit preferences? +

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

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

preferences is provided by the DomainKits MCP server (https://api.domainkits.com/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every DomainKits tool call.

Deterministic rules across all 38 DomainKits 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.