Lpm Registry

17 tools. 3 can modify or destroy data without limits.

3 write tools that can modify data. Rate limits recommended.

Last updated:

3 can modify or destroy data
14 read-only
17 tools total

Community server · catalogue entry verified 03/07/2026

How to control Lpm Registry ↓

What Lpm Registry exposes to your agents

Read (14) Write / Execute (3) Destructive / Financial (0)
High Risk

The most dangerous Lpm Registry tools

3 of Lpm Registry's 17 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Lpm Registry

PolicyLayer is an MCP gateway — it sits between your AI agents and Lpm Registry, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations
{
  "lpm_add": {
    "limits": [
      {
        "counter": "lpm_add_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "lpm_api_docs": {
    "limits": [
      {
        "counter": "lpm_api_docs_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Lpm Registry — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON LPM REGISTRY →

Instant setup, no code required.

All 17 Lpm Registry tools

READ 14 tools
Read lpm_api_docs Get structured API documentation for an LPM package — functions, classes, interfaces, type aliases, enums, and Read lpm_browse_source LAST RESORT: Browse source code of an LPM package remotely. Only use this when you cannot install the package Read lpm_docs Search or read LPM documentation. Use this when the user asks how to use LPM itself — setup, CLI commands, pub Read lpm_llm_context Get an LLM-optimized usage guide for an LPM package — purpose, quickStart code, key exports with signatures, c Read lpm_marketplace_info Get marketplace information for an LPM package — pricing, licensing model, seat management, and purchase statu Read lpm_package_context Get complete context for an LPM package in a single call — combines condensed package metadata (name, version, Read lpm_package_info Get metadata for an LPM package including versions, description, downloads, AI analysis, compatibility, and re Read lpm_package_skills Get author-written Agent Skills for an LPM package — usage patterns, anti-patterns, gotchas, and best practice Read lpm_packages_by_owner List packages published by a specific user or organization on the LPM registry. Shows public packages with dis Read lpm_pool_stats Get your Pool revenue sharing earnings estimate for the current month. Shows per-package breakdown with instal Read lpm_quality_report Get the quality score and detailed check breakdown for an LPM package (27 checks across documentation, code, t Read lpm_search Search LPM packages using natural language or structured filters. Uses hybrid semantic search for natural lang Read lpm_search_owners Search for users or organizations on the LPM registry by name or username. Read lpm_user_info Get information about the authenticated LPM user including organizations, plan tier, pool access, and usage li

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Lpm Registry

How do I prevent bulk modifications through Lpm Registry? +

The Lpm Registry server has 2 write tools including lpm_add, lpm_install. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Lpm Registry.

How many tools does the Lpm Registry MCP server expose? +

17 tools across 3 categories: Execute, Read, Write. 14 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on Lpm Registry? +

Register the Lpm Registry MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Lpm Registry tool call.

Deterministic rules across all 17 Lpm Registry tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

17 Lpm Registry tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.