Set the primary domain for an environment.
AI agents use kinsta.domains.set-primary to create or update resources in Kinsta MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kinsta MCP Server environment.
This tool modifies infrastructure configuration (primary domain assignment) which affects how sites are accessed and routed. While not destructive or irreversible (domain settings can be changed again), it is a consequential write operation on hosting infrastructure that could disrupt service routing if misconfigured by an AI agent. The high severity reflects potential for service disruption despite reversibility.
From the tool's definition Tool name 'set-primary' and description 'Set the primary domain for an environment' indicate modification of domain configuration.
Attacks that exploit this kind of access
Set the primary domain for an environment. It is categorised as a Write tool in the Kinsta MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kinsta MCP Server MCP server in PolicyLayer and add a rule for kinsta.domains.set-primary: 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 Kinsta MCP Server. Nothing to install.
kinsta.domains.set-primary 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 kinsta.domains.set-primary 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 kinsta.domains.set-primary. 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.
kinsta.domains.set-primary is provided by the Kinsta MCP Server MCP server (jacob-hartmann/kinsta-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →