kinsta.environments.php-allocation-site

WHAT IT DOES

What kinsta.environments.php-allocation-site does on Kinsta MCP Server

AI agents use kinsta.environments.php-allocation-site 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.environments.php-allocation-site needs a policy

This tool modifies the PHP worker allocation configuration for site environments. It's a configuration change (Write) rather than destructive since it can be reversed by changing the allocation again. However, misuse could cause performance degradation or outages if workers are set too low, hence medium severity.

From the tool's definition Change PHP worker allocation for all environments in a site

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

kinsta.environments.php-allocation-site Rate-limited

kinsta.environments.php-allocation-site 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.environments.php-allocation-site": {
      "limits": [
        {
          "counter": "kinsta.environments.php-allocation-site_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.environments.php-allocation-site

What does the kinsta.environments.php-allocation-site tool do? +

Change PHP worker allocation for all environments in 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.

How do I enforce a policy on kinsta.environments.php-allocation-site? +

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

kinsta.environments.php-allocation-site is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit kinsta.environments.php-allocation-site? +

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

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

kinsta.environments.php-allocation-site 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.