Search or read LPM documentation. Use this when the user asks how to use LPM itself — setup, CLI commands, publishing, CI/CD, Swift registry, organizations, billing, etc. Without parameters: returns the docs index. With
AI agents call lpm_docs to retrieve information from Lpm Registry without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries documentation content with no side effects. It is a standard documentation search/browse function that does not modify, execute, or delete any data. The severity is low because documentation access poses minimal risk — the worst outcome of misuse would be retrieving irrelevant or excessive documentation.
From the tool's definition Tool description states 'Search or read LPM documentation' and explicitly lists read-only use cases: 'setup, CLI commands, publishing, CI/CD, Swift registry, organizations, billing'.
Attacks that exploit this kind of access
Search or read LPM documentation. Use this when the user asks how to use LPM itself — setup, CLI commands, publishing, CI/CD, Swift registry, organizations, billing, etc. Without parameters: returns the docs index. With. It is categorised as a Read tool in the Lpm Registry MCP Server, which means it retrieves data without modifying state.
Register the Lpm Registry MCP server in PolicyLayer and add a rule for lpm_docs: 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.
lpm_docs is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the lpm_docs 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.
Set action: deny in the PolicyLayer policy for lpm_docs. 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.
lpm_docs 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →