Skip to main content
Glama
bishnubista

Vulnerable Notes MCP Server

by bishnubista

notes_delete

Delete a note by title from the Vulnerable Notes MCP Server. This tool removes notes immediately without requiring confirmation.

Instructions

Delete a note by title. Executes immediately without confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle of the note to delete

Implementation Reference

  • The handler logic for the 'notes_delete' tool, which deletes a file based on the provided title.
    case "notes_delete": {
      const { title } = args as { title: string };
      const filePath = getNotePath(title);
    
      // VULNERABILITY: SAFE-T1701 - No confirmation required
      // Dangerous operation executes immediately
      if (fs.existsSync(filePath)) {
        fs.unlinkSync(filePath);
        return {
          content: [{ type: "text", text: `Note "${title}" deleted` }],
        };
      }
    
      return {
        content: [{ type: "text", text: `Note "${title}" not found` }],
      };
    }
  • The schema/definition for the 'notes_delete' tool, specifying its input requirements.
      name: "notes_delete",
      description: "Delete a note by title. Executes immediately without confirmation.",
      inputSchema: {
        type: "object" as const,
        properties: {
          title: { type: "string", description: "Title of the note to delete" },
        },
        required: ["title"],
      },
    },
Behavior4/5

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

With no annotations provided, the description carries full burden and successfully discloses critical behavioral trait: immediate execution without confirmation. However, it omits error handling (what if title not found) and reversibility details.

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?

Extremely efficient two-sentence structure: first sentence states purpose, second discloses behavioral risk. No redundant or filler content; information density is optimal.

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?

Appropriate for a single-parameter destructive tool. The immediate-execution warning suffices given the simplicity, though mentioning error cases (e.g., title not found) would improve completeness.

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% (title parameter fully described), so baseline applies. Description reinforces that deletion is by title but does not add syntax constraints, validation rules, or uniqueness requirements beyond the schema.

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?

Description provides specific verb ('Delete'), resource ('note'), and scope ('by title'), clearly distinguishing it from sibling tools like notes_create, notes_read, and notes_cleanup.

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

Usage Guidelines3/5

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

Contains implicit usage guidance through the warning 'Executes immediately without confirmation,' but lacks explicit when-to-use criteria or differentiation from notes_cleanup for bulk operations.

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