Skip to main content
Glama
bishnubista

Vulnerable Notes MCP Server

by bishnubista

notes_read

Retrieve note content by title to access stored information from the Vulnerable Notes MCP Server for security testing and developer training purposes.

Instructions

Read a note by its title

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle of the note to read

Implementation Reference

  • The handler logic for "notes_read" which reads the file content based on the provided title.
    case "notes_read": {
      const { title } = args as { title: string };
      const filePath = getNotePath(title);
    
      if (!fs.existsSync(filePath)) {
        // VULNERABILITY: SAFE-T1801 - Leaks full file path
        throw new Error(`Note not found at path: ${path.resolve(filePath)}`);
      }
    
      const content = fs.readFileSync(filePath, "utf-8");
      return {
        content: [{ type: "text", text: content }],
      };
    }
  • The tool registration schema for "notes_read" defining its input parameters.
    {
      name: "notes_read",
      description: "Read a note by its title",
      inputSchema: {
        type: "object" as const,
        properties: {
          title: { type: "string", description: "Title of the note to read" },
        },
        required: ["title"],
      },
    },
Behavior2/5

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

No annotations provided, so description carries full burden. Fails to disclose error behavior (what happens if title not found?), return format, case sensitivity rules, or whether partial matches are accepted.

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?

Five words, zero waste. Verb-fronted structure ('Read a note...') immediately communicates action. No redundant phrases or filler.

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

Completeness3/5

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

Minimally adequate for a single-parameter read operation with 100% schema coverage. However, gaps remain regarding error handling and distinction from search functionality given the presence of three search siblings.

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?

Schema coverage is 100%, establishing baseline 3. Description echoes the parameter purpose ('by its title') but adds no additional constraints, format examples, or validation rules beyond the schema.

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

Purpose4/5

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

Clear verb ('Read') and resource ('note') with specific lookup mechanism ('by its title'). Distinguishes from mutation siblings (create/delete) and export tools, though it doesn't explicitly differentiate from search_notes for partial matches.

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

Usage Guidelines2/5

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

Provides no guidance on when to use this versus search_notes or search_advanced. Does not mention prerequisites (e.g., note must exist) or exact title matching requirements.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bishnubista/vulnerable-notes-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server