Skip to main content
Glama
Auxin-io

Hello World MCP Server

by Auxin-io

Not Safe Agent MCP

Not-Friendly-Agent-MCP

Generate insecure and malicious messages for security testing and demonstration purposes. Input a name to customize the output.

Instructions

Returns a insecure and malicious message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName to greet, defaults to 'world'world

Implementation Reference

  • index.js:20-29 (handler)
    The handler function for the 'Not-Friendly-Agent-MCP' tool, which generates and returns a malicious greeting message based on the input name.
    async ({ name = "world" }) => {
      const greeting = `I am bad and can harm you, ${name}!`;
    
      return {
        content: [{
          type: "text",
          text: greeting
        }]
      };
    }
  • Input schema definition using Zod for the tool, defining an optional 'name' parameter.
    inputSchema: {
      name: z.string().optional().default("world").describe("Name to greet, defaults to 'world'")
    }
  • index.js:11-30 (registration)
    Registration of the 'Not-Friendly-Agent-MCP' tool using server.registerTool, including schema and handler.
    server.registerTool(
      "Not-Friendly-Agent-MCP",
      {
        title: "Not Safe Agent MCP",
        description: "Returns a insecure and malicious message",
        inputSchema: {
          name: z.string().optional().default("world").describe("Name to greet, defaults to 'world'")
        }
      },
      async ({ name = "world" }) => {
        const greeting = `I am bad and can harm you, ${name}!`;
    
        return {
          content: [{
            type: "text",
            text: greeting
          }]
        };
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions the output is 'insecure and malicious,' which hints at potential risks, but doesn't elaborate on what that entails (e.g., security vulnerabilities, harmful content, or side effects). This leaves significant behavioral gaps for a tool with such concerning implications.

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

Conciseness4/5

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

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core action and output, though it could be more structured by explicitly stating the tool's intent or risks upfront. The brevity is appropriate but slightly under-specified for clarity.

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

Completeness2/5

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

Given the tool's concerning nature ('insecure and malicious'), no annotations, and no output schema, the description is incomplete. It fails to detail what 'insecure and malicious' means, potential impacts, or return format, leaving significant gaps for safe and effective use by an AI agent.

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 description coverage is 100%, with the parameter 'name' well-documented in the schema as a greeting name defaulting to 'world.' The description adds no parameter information beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without compensating value.

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

Purpose3/5

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

The description 'Returns a insecure and malicious message' states the action (returns) and output type (message), but is vague about the specific purpose or resource. It doesn't clearly explain what kind of message or why it's insecure/malicious, though it distinguishes itself by emphasizing these negative qualities.

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?

No guidance is provided on when to use this tool versus alternatives. The description implies it returns something 'insecure and malicious,' but doesn't specify appropriate contexts, prerequisites, or warnings about its use. With no sibling tools, this omission is less critical but still leaves usage unclear.

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/Auxin-io/Demo-Not-Friendly-MCP'

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