kinsta.environments.redirects.update

Create, update, or delete redirect rules for an environment.

Server Kinsta MCP Server jacob-hartmann/kinsta-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What kinsta.environments.redirects.update does on Kinsta MCP Server

AI agents call kinsta.environments.redirects.update to permanently remove resources in Kinsta MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why kinsta.environments.redirects.update needs a policy

Since the tool can delete redirect rules in addition to creating and updating them, and deletion is irreversible, the most severe applicable category is Destructive. Misconfiguration or deletion of redirect rules on a WordPress hosting environment could break site routing, causing outages or misdirected traffic across the entire environment.

From the tool's definition 'Create, update, or delete redirect rules for an environment' — the tool explicitly includes deletion of redirect rules, which is irreversible. It also spans Write (create/update) and Destructive (delete) categories.

Questions about kinsta.environments.redirects.update

What does the kinsta.environments.redirects.update tool do? +

Create, update, or delete redirect rules for an environment. It is categorised as a Destructive tool in the Kinsta MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on kinsta.environments.redirects.update? +

Register the Kinsta MCP Server MCP server in PolicyLayer and add a rule for kinsta.environments.redirects.update: 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.

What risk level is kinsta.environments.redirects.update? +

kinsta.environments.redirects.update is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit kinsta.environments.redirects.update? +

Yes. Add a rate_limit block to the kinsta.environments.redirects.update 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 kinsta.environments.redirects.update completely? +

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

kinsta.environments.redirects.update 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.