lpm_audit · Lpm Registry MCP: Risk & Policy

WHAT IT DOES

What lpm_audit does on Lpm Registry

AI agents invoke lpm_audit to trigger actions in Lpm Registry. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why lpm_audit needs a policy

This tool executes a security audit operation, which involves running code or external processes to analyze the project. While audits are typically informational (Read-adjacent), the verb 'Run' and the nature of security audits—which often execute static analysis, dependency checks, or other scanning operations—places this in the Execute category.

From the tool's definition Tool name 'lpm_audit' combined with description 'Run a security audit on the project' indicates execution of an external audit process or security scanning tool.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lpm_audit Rate-limited

lpm_audit stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lpm_audit": {
      "limits": [
        {
          "counter": "lpm_audit_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Lpm Registry, so you can run agents against it safely.

FAQ

Questions about lpm_audit

What does the lpm_audit tool do? +

Run a security audit on the project. It is categorised as a Execute tool in the Lpm Registry MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on lpm_audit? +

Register the Lpm Registry MCP server in PolicyLayer and add a rule for lpm_audit: 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.

What risk level is lpm_audit? +

lpm_audit is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit lpm_audit? +

Yes. Add a rate_limit block to the lpm_audit 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.

How do I block lpm_audit completely? +

Set action: deny in the PolicyLayer policy for lpm_audit. 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.

What MCP server provides lpm_audit? +

lpm_audit 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.