Manage custom domains for a service
AI agents use manage_domains to create or update resources in Render — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Render environment.
Domain management involves configuration changes that are reversible (domains can be added, updated, or removed without permanent data loss). This falls under Write rather than Execute because it modifies service settings rather than triggering arbitrary external operations. It is not Destructive since domain changes are reversible.
From the tool's definition Tool name 'manage_domains' and description 'Manage custom domains for a service' indicate operations that create, modify, or update domain configurations for services on Render. 'Manage' typically encompasses adding, updating, or removing domain associations.
Documented attack patterns abuse exactly the kind of access manage_domains gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Render, and nothing reaches the server without passing your rules. This is the rule we recommend for manage_domains:
{
"version": "1",
"default": "deny",
"tools": {
"manage_domains": {
"limits": [
{
"counter": "manage_domains_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}manage_domains stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Manage custom domains for a service. It is categorised as a Write tool in the Render MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Render MCP server in PolicyLayer and add a rule for manage_domains: 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 Render. Nothing to install.
manage_domains is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the manage_domains 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 manage_domains. 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.
manage_domains is provided by the Render MCP server (niyogi/render-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Render, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Render tools catalogued and risk-classified — across an index of 43,000+ MCP servers.