Medium Risk

domain_settings

Update domain settings (auto-renew, WHOIS privacy, registrar lock). Only provided (non-None) fields are updated. Requires: API key with write scope. Args: domain_name: Full domain name (e.g. "example.com") auto_renew: Enable/disable automatic renewal whois_privacy: Enable/disable WHOIS privacy pr...

Part of the BorealHost server.

domain_settings can modify BorealHost data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE BOREALHOST →

Free to start. No card required.

AI agents use domain_settings to create or modify resources in BorealHost. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call domain_settings repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach BorealHost.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "domain_settings": {
      "limits": [
        {
          "counter": "domain_settings_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full BorealHost policy for all 95 tools.

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

ENFORCE ON MY BOREALHOST →

View all 95 tools →

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

SECURE BOREALHOST →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the domain_settings tool do? +

Update domain settings (auto-renew, WHOIS privacy, registrar lock). Only provided (non-None) fields are updated. Requires: API key with write scope. Args: domain_name: Full domain name (e.g. "example.com") auto_renew: Enable/disable automatic renewal whois_privacy: Enable/disable WHOIS privacy protection locked: Enable/disable registrar lock (prevents unauthorized transfers) Returns: {"success": true, "domain": "example.com", "auto_renew": true, "whois_privacy": true, "locked": true} Errors: NOT_FOUND: Domain not found or not owned by account. It is categorised as a Write tool in the BorealHost MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on domain_settings? +

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

What risk level is domain_settings? +

domain_settings is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit domain_settings? +

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

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

domain_settings is provided by the BorealHost MCP server (pypi:borealhost-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every BorealHost tool call.

Deterministic rules across all 95 BorealHost 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.