Get metadata for an LPM package including versions, description, downloads, AI analysis, compatibility, and readme
AI agents call lpm_package_info 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 performs a query/lookup operation to retrieve package metadata without side effects. It does not create, modify, delete, execute code, or move funds. It is purely informational, similar to browsing package information on a registry website.
From the tool's definition Tool description states it 'Get metadata for an LPM package' — a retrieval operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Get metadata for an LPM package including versions, description, downloads, AI analysis, compatibility, and readme. 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_package_info: 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_package_info 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_package_info 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_package_info. 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_package_info 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 →