Get the quality score and detailed check breakdown for an LPM package (27 checks across documentation, code, testing, health)
AI agents call lpm_quality_report 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 queries package quality data from a registry and returns analysis results. It performs no write operations, does not execute code, does not delete data, and does not affect system state. The action is a straightforward data retrieval matching the Read category pattern (get, fetch).
From the tool's definition Tool retrieves and reports quality metrics and check breakdowns for a package. The description states it 'Get[s] the quality score and detailed check breakdown' — purely informational output with no modification, execution, or side effects.
Attacks that exploit this kind of access
Get the quality score and detailed check breakdown for an LPM package (27 checks across documentation, code, testing, health). 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_quality_report: 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_quality_report 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_quality_report 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_quality_report. 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_quality_report 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 →