Skip to main content

What is Security Testing?

Security testing validates that your MCP server properly implements authentication, authorization, and protection against common vulnerabilities. It ensures your server can safely handle untrusted inputs and enforce access controls correctly.

Key Benefits

  • Authentication validation - Verify auth flows work correctly
  • Access control testing - Ensure permissions are enforced
  • Vulnerability detection - Find injection attacks and other security issues
  • Rate limiting verification - Test DoS protection mechanisms

How It Works

Configuration

Basic Security Test Suite

Test Configuration Fields

Suite-Level Settings

Authentication Methods

1. OAuth Authentication

Test OAuth flows and token security:
Tests:
  • OAuth token validation
  • Authorization flow security
  • Token refresh handling
  • Scope enforcement

2. Token Authentication

Test bearer token security:
Tests:
  • Bearer token validation
  • Token expiration handling
  • Token manipulation detection
  • Authentication bypass prevention

Vulnerability Testing

Available Vulnerability Checks

MCP-Specific Security Tests

  • Prompt Injection (mcp_prompt_injection): Tests resistance to prompt manipulation attacks
  • Data Leakage (mcp_data_leakage): Detects sensitive information exposure through responses
  • Authentication Bypass (authentication_bypass): Validates permission enforcement

Input Validation Tests

Security Test Examples

1. OAuth Security Testing

2. Input Sanitization Testing

Running Security Tests

Create Security Test Suite

Run Security Tests

Example Command Flow

Configuration Files

The framework includes example security configurations:

Pre-built Security Suite

Location: configs/suites/security-tests.json

OAuth-Specific Security Suite

Location: configs/suites/oauth-security-tests.json

Security Issue Severity Levels

Critical Issues

  • Remote code execution vulnerabilities
  • Authentication bypass flaws
  • Complete authorization bypass
  • Data exposure vulnerabilities

High Severity

  • Privilege escalation vectors
  • Token manipulation vulnerabilities
  • OAuth flow vulnerabilities
  • Sensitive information disclosure

Medium Severity

  • Input validation gaps
  • Minor authentication issues
  • Configuration weaknesses
  • Rate limiting issues

Low Severity

  • Information leakage (non-sensitive)
  • Logging and monitoring gaps
  • Documentation security concerns

Next Steps

  1. CLI Reference
  2. Server Configuration for auth setup
  3. Compliance Testing for protocol validation
  4. Conversational Testing for user experience