kinsta.dns.records.update · Kinsta MCP Server MCP

WHAT IT DOES

What kinsta.dns.records.update does on Kinsta MCP Server

AI agents use kinsta.dns.records.update 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.

WHY IT NEEDS A POLICY

Why kinsta.dns.records.update needs a policy

DNS record updates are reversible modifications that can alter domain routing, email configuration, and security settings. While not destructive (records can be reverted) or financial, misuse could redirect traffic to attacker infrastructure, intercept email, or disable services.

From the tool's definition Tool name is 'kinsta.dns.records.update' and description states it will 'Update an existing DNS record for a domain.' The word 'Update' indicates modification of existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

kinsta.dns.records.update Rate-limited

kinsta.dns.records.update 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "kinsta.dns.records.update": {
      "limits": [
        {
          "counter": "kinsta.dns.records.update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Kinsta MCP Server, so you can run agents against it safely.

FAQ

Questions about kinsta.dns.records.update

What does the kinsta.dns.records.update tool do? +

Update an existing DNS record for a domain. 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.

How do I enforce a policy on kinsta.dns.records.update? +

Register the Kinsta MCP Server MCP server in PolicyLayer and add a rule for kinsta.dns.records.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.dns.records.update? +

kinsta.dns.records.update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit kinsta.dns.records.update? +

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

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

kinsta.dns.records.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.