dc_generate_commissioning_plan

WHAT IT DOES

What dc_generate_commissioning_plan does on Datacenter

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

WHY IT NEEDS A POLICY

Why dc_generate_commissioning_plan needs a policy

Generating a commissioning plan creates new data (planning documents, procedures, configurations) that are written to a system but are typically reversible through standard edit/update operations. This is a Write operation, not destructive since commissioning plans can be modified or discarded.

From the tool's definition Tool name contains 'generate' and 'plan' in a commissioning workflow context. The server description states it provides 'commissioning workflows' as a core function. Commissioning plans involve creating operational procedures and documentation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dc_generate_commissioning_plan Rate-limited

dc_generate_commissioning_plan 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": {
    "dc_generate_commissioning_plan": {
      "limits": [
        {
          "counter": "dc_generate_commissioning_plan_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 Datacenter, so you can run agents against it safely.

FAQ

Questions about dc_generate_commissioning_plan

What does the dc_generate_commissioning_plan tool do? +

dc_generate_commissioning_plan. It is categorised as a Write tool in the Datacenter MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on dc_generate_commissioning_plan? +

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

What risk level is dc_generate_commissioning_plan? +

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

Can I rate-limit dc_generate_commissioning_plan? +

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

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

dc_generate_commissioning_plan is provided by the Datacenter MCP server (log-wade/datacenter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.