kinsta.tools.restart-php · Kinsta MCP Server MCP

WHAT IT DOES

What kinsta.tools.restart-php does on Kinsta MCP Server

AI agents invoke kinsta.tools.restart-php to trigger actions in Kinsta MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why kinsta.tools.restart-php needs a policy

This tool executes a command (PHP restart) on live infrastructure with externally-visible effects. While not destructive (data is not deleted) and not financial, it directly triggers code execution and service interruption in a production environment, matching the Execute category.

From the tool's definition Tool performs 'Restart PHP for an environment' — a direct operational action that triggers external infrastructure behavior. Returns an operation_id, indicating an async operation is initiated on the host system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

kinsta.tools.restart-php Rate-limited

kinsta.tools.restart-php stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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.tools.restart-php": {
      "limits": [
        {
          "counter": "kinsta.tools.restart-php_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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.tools.restart-php

What does the kinsta.tools.restart-php tool do? +

Restart PHP for an environment. Returns an operation_id. It is categorised as a Execute tool in the Kinsta MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on kinsta.tools.restart-php? +

Register the Kinsta MCP Server MCP server in PolicyLayer and add a rule for kinsta.tools.restart-php: 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.tools.restart-php? +

kinsta.tools.restart-php is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit kinsta.tools.restart-php? +

Yes. Add a rate_limit block to the kinsta.tools.restart-php 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.tools.restart-php completely? +

Set action: deny in the PolicyLayer policy for kinsta.tools.restart-php. 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.tools.restart-php? +

kinsta.tools.restart-php 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.