Search for users or organizations on the LPM registry by name or username.
AI agents call lpm_search_owners 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 publicly available user and organization metadata from a package registry. It has no side effects—it does not create, modify, delete, or execute anything. The data returned is informational and non-sensitive in nature. Misuse would have minimal blast radius (e.g., reconnaissance for social engineering, but not actionable harm to systems or data).
From the tool's definition Tool searches for users/organizations 'by name or username' on the LPM registry. The verb 'search' and the read-only nature of querying user/organization information indicates retrieval without modification.
Attacks that exploit this kind of access
Search for users or organizations on the LPM registry by name or username. 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_search_owners: 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_search_owners 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_search_owners 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_search_owners. 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_search_owners 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 →