write_plm_configuration

WHAT IT DOES

What write_plm_configuration does on Infrastructure Auto Provisioner

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

WHY IT NEEDS A POLICY

Why write_plm_configuration needs a policy

This tool creates or modifies Pulumi configuration files, which are reversible operations (configurations can be edited or reverted). While configuration changes can have downstream effects when applied via sibling 'apply_plm_project_infrastructure' tools, the write operation itself is not executing infrastructure changes—it is preparing configuration data.

From the tool's definition Tool name 'write_plm_configuration' and description 'Write a pulumi configuration file' indicate creation/modification of configuration files.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

write_plm_configuration Rate-limited

write_plm_configuration 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": {
    "write_plm_configuration": {
      "limits": [
        {
          "counter": "write_plm_configuration_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 Infrastructure Auto Provisioner, so you can run agents against it safely.

FAQ

Questions about write_plm_configuration

What does the write_plm_configuration tool do? +

Write a pulumi configuration file. It is categorised as a Write tool in the Infrastructure Auto Provisioner MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on write_plm_configuration? +

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

What risk level is write_plm_configuration? +

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

Can I rate-limit write_plm_configuration? +

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

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

write_plm_configuration is provided by the Infrastructure Auto Provisioner MCP server (zerosync-co/mcp-server-autoprovisioner). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.