cfgaudit

OWASP Top 10 for LLM Applications and MCP

The OWASP Top 10 for LLM Applications 2026 is cfgaudit's primary mapping: every rule belongs to one of its categories. cfgaudit's 116 rules cover 4 of the ten in the files that configure an agent. The remaining 6 are about training data, providers, model output and application code, which a configuration file doesn't contain.

  1. LLM01

    Prompt Injection

    14 rules

    Text the agent reads as trusted context tells it to do something else: override phrases, hidden Unicode, fake turn boundaries and concealment orders in CLAUDE.md, AGENTS.md, rules files, skills and commands.

  2. Secrets and private files reach the model or leave the machine: credentials committed in settings and MCP configs, missing deny rules for .env and keys, commands that read credential files or send data to a remote host.

  3. LLM03

    Excessive Agency

    52 rules

    The agent can do more than the task needs without asking: unrestricted shell and write permissions, bypass and YOLO modes, auto-approved MCP servers, hooks that run on every session, instructions not to ask for confirmation.

  4. LLM04

    Supply Chain

    16 rules

    Code the agent runs can change under it: unpinned MCP packages and images, plugins and marketplaces controlled by a committed file, remote installers piped into a shell, skills that ask to run a downloaded archive.

  5. LLM05

    Data and Model Poisoning

    not in a configuration file

    Training data, fine-tuning sets and model weights are not part of an agent's configuration files.

  6. LLM06

    Unbounded Consumption

    not in a configuration file

    Rate limits, quotas and spending caps are set at the model provider or gateway, not in the repository.

  7. LLM07

    Misinformation

    not in a configuration file

    Whether an answer is correct is a property of the model's output at run time, not of the files that configure the agent.

  8. LLM08

    Hidden Context Exposure

    not in a configuration file

    What a model reveals of its hidden context happens in a conversation, after the configuration has been read.

  9. LLM09

    Vector and Embedding Weaknesses

    not in a configuration file

    Vector stores and retrieval pipelines live in the application, not in the agent's configuration files.

  10. LLM10

    Improper Output Handling

    not in a configuration file

    How an application handles model output is in its code, which cfgaudit does not analyse.

OWASP MCP Top 10

Rules about MCP servers also name a category of the OWASP MCP Top 10. They cover 8 of its ten risks.

  1. Tokens and keys written into MCP server definitions, headers and environment blocks.

  2. Servers that are approved wholesale or get more access than one task needs.

  3. MCP03

    Tool Poisoning

    1 rule

    Tool and server metadata that carries instructions for the model.

  4. Server packages and images that are not pinned and can change after review.

  5. Server commands that are inline shell scripts or interpreters running code from their arguments.

  6. Content the server returns that the agent is told to trust or act on.

  7. Remote servers reached without authentication or over plain HTTP.

  8. MCP08

    Lack of Audit and Telemetry

    not in a configuration file

    Audit logs and telemetry of MCP calls are produced at run time, not declared in a configuration file.

  9. MCP09

    Shadow MCP Servers

    1 rule

    Servers that take over a trusted name or are added without review.

  10. MCP10

    Context Injection & Over-Sharing

    not in a configuration file

    What context a server receives during a session depends on the conversation, not on the committed configuration.

Category names and links are from OWASP's lists. A rule names one LLM category and at most one MCP category.