plane-instance-config-update · Plane MCP: Risk & Policy

WHAT IT DOES

What plane-instance-config-update does on Plane

AI agents use plane-instance-config-update to create or update resources in Plane — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Plane environment.

WHY IT NEEDS A POLICY

Why plane-instance-config-update needs a policy

This tool modifies instance-level configuration, which is reversible but has significant blast radius. It allows changing authentication mechanisms (signup enable/disable, login methods), email settings, LLM providers and credentials, and workspace creation policies.

From the tool's definition Tool description states 'Update instance configuration keys' with examples including ENABLE_SIGNUP, ENABLE_MAGIC_LINK_LOGIN, EMAIL_HOST_PASSWORD, LLM_API_KEY, GOOGLE_CLIENT_SECRET—sensitive authentication and system settings that can be modified via key-value…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

plane-instance-config-update Rate-limited

plane-instance-config-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": {
    "plane-instance-config-update": {
      "limits": [
        {
          "counter": "plane-instance-config-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 Plane, so you can run agents against it safely.

FAQ

Questions about plane-instance-config-update

What does the plane-instance-config-update tool do? +

Update instance configuration keys. Pass key-value pairs. Example keys: ENABLE_SIGNUP, ENABLE_MAGIC_LINK_LOGIN, ENABLE_EMAIL_PASSWORD, IS_GOOGLE_ENABLED, GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, EMAIL_HOST, EMAIL_HOST_USER, EMAIL_HOST_PASSWORD, EMAIL_PORT, EMAIL_FROM, LLM_PROVIDER, LLM_MODEL, LLM_API_KEY, UNSPLASH_ACCESS_KEY, DISABLE_WORKSPACE_CREATION. It is categorised as a Write tool in the Plane MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on plane-instance-config-update? +

Register the Plane MCP server in PolicyLayer and add a rule for plane-instance-config-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 Plane. Nothing to install.

What risk level is plane-instance-config-update? +

plane-instance-config-update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit plane-instance-config-update? +

Yes. Add a rate_limit block to the plane-instance-config-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 plane-instance-config-update completely? +

Set action: deny in the PolicyLayer policy for plane-instance-config-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 plane-instance-config-update? +

plane-instance-config-update is provided by the Plane MCP server (philipvanlewis/plane-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.