High Risk →

aged

Search currently registered domains with 5-20+ years of history. These are live domains owned by someone — not available for free registration. Use has_sale=true to filter to domains the owner has listed for sale, or use results as acquisition targets to approach owners directly. Best practices: ...

Risk signalsHigh parameter count (12 properties)

Part of the DomainKits server.

aged can trigger actions 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 invoke aged to trigger processes or run actions in DomainKits. 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.

aged 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "aged": {
      "limits": [
        {
          "counter": "aged_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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 aged 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 aged only ever does what you allow.

SECURE DOMAINKITS →

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

What does the aged tool do? +

Search currently registered domains with 5-20+ years of history. These are live domains owned by someone — not available for free registration. Use has_sale=true to filter to domains the owner has listed for sale, or use results as acquisition targets to approach owners directly. Best practices: - Always use no_hyphen=true and no_number=true unless the user specifically wants them. - keyword defaults to 'contain' matching, which searches all domains containing the keyword anywhere in the name. Use position=start, position=end, or position=middle to control where the keyword appears. - has_sale=true is the most actionable filter — these owners are actively seeking buyers. - Caution: Many aged domains are already in active use as established brands. Before recommending an aged domain to a user, consider whether it is likely an operating business — a 20-year-old short .com is almost certainly in use. - Short domains (<5 chars) with 20+ years of history are rare and typically high-value. Most 4-letter .coms were registered over 20 years ago. - For premium brand hunting: combine length=<5 or 5-10, type=all_alpha, no_hyphen=true, age_range=20+. - sort=age_desc surfaces the oldest domains first. sort=length_asc surfaces the shortest. - Disclose affiliate links when presenting register_url to users.. It is categorised as a Execute tool in the DomainKits MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on aged? +

Register the DomainKits MCP server in PolicyLayer and add a rule for aged: 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 aged? +

aged is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit aged? +

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

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

aged 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.