AgentAudit

audit_package

Clones a Git repository and performs a three-pass security audit (UNDERSTAND, DETECT, CLASSIFY) to identify vulnerabilities, prompt injection, and supply chain attacks.

Instructions

Deep security audit of a Git repository. Clones the repo and returns source code with a 3-pass audit methodology (UNDERSTAND → DETECT → CLASSIFY). You then analyze the code and call submit_report with findings. Use check_package FIRST to see if an audit already exists — only use this for unaudited packages or when a fresh audit is requested.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "source_url": "<source_url>"
    },
    "name": "audit_package"
  }
}

Input Schema

Name	Required	Description	Default
`source_url`	Yes	Git repository URL to audit (e.g., https://github.com/owner/repo)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.14.0Jun 8, 2026

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It discloses that it clones the repo, returns source code, and mentions a 3-pass methodology. However, it is slightly ambiguous whether the methodology is executed by the tool or is a guide for the agent, and it does not mention side effects like repository size limits or auth needs. Still, the core behavior is transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences, each serving a purpose: the first defines the core action, the second describes the workflow, and the third provides usage guidance. It is concise, front-loaded, and free of fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the tool's purpose, when to use it, and the follow-up action, which is sufficient for a one-parameter tool with no output schema. However, it leaves some details ambiguous, such as the exact output format and how the 3-pass methodology manifests, but overall the context is well covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema fully documents the single parameter 'source_url' with a description and example. The tool description does not add specific parameter-level details beyond what the schema already provides, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool performs a 'deep security audit of a Git repository' with a specific verb and resource. It distinguishes itself from siblings by explicitly mentioning check_package and submit_report, positioning this tool as the core auditing step.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit guidance: 'Use check_package FIRST to see if an audit already exists — only use this for unaudited packages or when a fresh audit is requested.' It also instructs to call submit_report with findings after analysis, clearly defining when and how to use the tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server