update_site_env · Ploi MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_site_env does on Ploi MCP Server

AI agents use update_site_env to create or update resources in Ploi MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ploi MCP Server environment.

WHY IT NEEDS A POLICY

Why update_site_env needs a policy

This tool modifies site environment variables or configuration reversibly. While 'replace' suggests overwriting, it is not a deletion operation (which would be Destructive) but rather a configuration update (Write). The severity is high because misconfiguring site environment variables could disrupt service availability or expose secrets, though the action is technically reversible by updating again.

From the tool's definition Tool is named 'update_site_env' and described as 'Replace a site'. The 'Replace' verb indicates modification of existing site configuration/environment variables, which is reversible (can be updated again).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_site_env Rate-limited

update_site_env 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": {
    "update_site_env": {
      "limits": [
        {
          "counter": "update_site_env_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 Ploi MCP Server, so you can run agents against it safely.

FAQ

Questions about update_site_env

What does the update_site_env tool do? +

Replace a site. It is categorised as a Write tool in the Ploi 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 update_site_env? +

Register the Ploi MCP Server MCP server in PolicyLayer and add a rule for update_site_env: 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 Ploi MCP Server. Nothing to install.

What risk level is update_site_env? +

update_site_env is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_site_env? +

Yes. Add a rate_limit block to the update_site_env 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 update_site_env completely? +

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

update_site_env is provided by the Ploi MCP Server MCP server (sudanese/ploi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.