List packages published by a specific user or organization on the LPM registry. Shows public packages with distribution mode.
AI agents call lpm_packages_by_owner 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.
The tool queries and returns information about publicly available packages. It performs a straightforward lookup/list operation without creating, modifying, deleting, executing code, or moving resources. The data retrieved is public package metadata with no destructive or financial implications.
From the tool's definition Tool description states 'List packages published by a specific user or organization' and 'Shows public packages' - these are retrieval operations with no modification or side effects.
Attacks that exploit this kind of access
List packages published by a specific user or organization on the LPM registry. Shows public packages with distribution mode. 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_packages_by_owner: 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_packages_by_owner 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_packages_by_owner 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_packages_by_owner. 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_packages_by_owner 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 →