install_plm_project_dependency

WHAT IT DOES

What install_plm_project_dependency does on Infrastructure Auto Provisioner

AI agents invoke install_plm_project_dependency to trigger actions in Infrastructure Auto Provisioner. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why install_plm_project_dependency needs a policy

Installing a dependency executes package management operations on the infrastructure project, running external commands and modifying the project environment. This is an Execute-level action as it triggers external operations (package installation) that can have significant side effects on infrastructure configuration.

From the tool's definition Install pulumi infrastructure project dependency

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

install_plm_project_dependency Rate-limited

install_plm_project_dependency stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "install_plm_project_dependency": {
      "limits": [
        {
          "counter": "install_plm_project_dependency_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 install_plm_project_dependency

What does the install_plm_project_dependency tool do? +

Install pulumi infrastructure project dependency. It is categorised as a Execute tool in the Infrastructure Auto Provisioner MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on install_plm_project_dependency? +

Register the Infrastructure Auto Provisioner MCP server in PolicyLayer and add a rule for install_plm_project_dependency: 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 install_plm_project_dependency? +

install_plm_project_dependency is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit install_plm_project_dependency? +

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

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

install_plm_project_dependency 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.