Create a new WordPress site on Kinsta. Returns an operation_id to track progress.
AI agents use kinsta.sites.create 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 creates a new WordPress site, which is a reversible write operation (the site can be deleted later). While it provisions infrastructure and incurs potential costs, the primary action is resource creation rather than financial commitment or irreversible destruction.
From the tool's definition Tool name 'kinsta.sites.create' and description 'Create a new WordPress site on Kinsta' explicitly indicates creation of new infrastructure/resources.
Attacks that exploit this kind of access
Create a new WordPress site on Kinsta. Returns an operation_id to track progress. 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.sites.create: 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.sites.create 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.sites.create 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.sites.create. 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.sites.create 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 →