Skip to main content
Glama
LexiconAlex

Better Auth MCP Server

by LexiconAlex

test_security

Run security tests on authentication setups to verify password policies, rate limiting, and session management configurations.

Instructions

Run security tests on Better-Auth setup

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
testsYes

Implementation Reference

  • Handler for the 'test_security' tool. Extracts 'tests' array from arguments, logs the tests being run, and returns a success message indicating completion of security tests.
    case "test_security": {
      const { tests } = request.params.arguments as { tests: string[] };
      logger.info(`Running security tests: ${tests.join(", ")}`);
      // Implementation would run security tests
      return {
        content: [{
          type: "text",
          text: `Security tests completed for: ${tests.join(", ")}`
        }]
      };
    }
  • Input schema for 'test_security' tool defining an object with a 'tests' array property, where items are strings from the enum ['password-policy', 'rate-limiting', 'session-management'], and 'tests' is required.
    inputSchema: {
      type: "object",
      properties: {
        tests: {
          type: "array",
          items: {
            type: "string",
            enum: ["password-policy", "rate-limiting", "session-management"]
          }
        }
      },
      required: ["tests"]
    }
  • src/index.ts:151-167 (registration)
    Registration of the 'test_security' tool in the ListToolsRequestHandler, including name, description, and input schema.
    {
      name: "test_security",
      description: "Run security tests on Better-Auth setup",
      inputSchema: {
        type: "object",
        properties: {
          tests: {
            type: "array",
            items: {
              type: "string",
              enum: ["password-policy", "rate-limiting", "session-management"]
            }
          }
        },
        required: ["tests"]
      }
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Run security tests' but doesn't specify what this entails—whether it's a read-only diagnostic, a destructive test, requires specific permissions, has side effects, or details about output format. This leaves significant gaps for a security testing tool.

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 a single, efficient sentence with no wasted words, clearly front-loading the core action. It's appropriately sized for a simple tool, making it easy to parse quickly.

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 complexity of security testing, no annotations, no output schema, and low schema coverage, the description is inadequate. It lacks details on behavior, parameters, and expected results, making it incomplete for effective tool selection and invocation.

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

Parameters2/5

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

Schema description coverage is 0%, and the description provides no information about the 'tests' parameter beyond what's implied by the tool name. It doesn't explain the enum values ('password-policy', 'rate-limiting', 'session-management') or their meanings, failing to compensate for the low schema coverage.

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?

The description clearly states the verb ('Run') and resource ('security tests') with specific context ('on Better-Auth setup'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'test_auth_flows' or 'analyze_current_auth', which might cover overlapping security aspects.

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 like 'test_auth_flows' or 'analyze_current_auth'. The description lacks context about prerequisites, timing, or exclusions, leaving the agent to infer usage based on tool names alone.

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/LexiconAlex/better-auth-mcp-server'

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