Create a new plain (empty) environment for a site. Returns an operation_id.
AI agents use kinsta.environments.create-plain 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.
The tool creates a new environment, which is a write operation that modifies infrastructure state. It is reversible (the environment can be deleted), so it does not qualify as Destructive.
From the tool's definition Tool name includes 'create' and description states 'Create a new plain (empty) environment for a site.' This is a reversible creation operation.
Attacks that exploit this kind of access
Create a new plain (empty) environment for a site. Returns an operation_id. 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.environments.create-plain: 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.environments.create-plain 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.environments.create-plain 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.environments.create-plain. 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.environments.create-plain 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 →