lpm_add · Lpm Registry MCP: Risk & Policy

WHAT IT DOES

What lpm_add does on Lpm Registry

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

WHY IT NEEDS A POLICY

Why lpm_add needs a policy

The tool adds package files to a project and extracts source code for customization, which is a reversible write operation (files can be deleted or the package removed). It does not execute arbitrary code, delete irreversibly, or handle financial transactions.

From the tool's definition 'Add an LPM package to the project by extracting source files for customization' — this action modifies the project by adding and extracting package files, creating new content that can be reversed by removing the package.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lpm_add Rate-limited

lpm_add 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": {
    "lpm_add": {
      "limits": [
        {
          "counter": "lpm_add_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 Lpm Registry, so you can run agents against it safely.

FAQ

Questions about lpm_add

What does the lpm_add tool do? +

Add an LPM package to the project by extracting source files for customization. Use for UI components, blocks, templates, and MCP servers. Requires LPM CLI installed. It is categorised as a Write tool in the Lpm Registry MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on lpm_add? +

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

What risk level is lpm_add? +

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

Can I rate-limit lpm_add? +

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

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

lpm_add is provided by the Lpm Registry MCP server (lpm-dev/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.