PraisonAI is a multi-agent teams system. From 1.5.1 until 1.7.2, MCPSecurity.evaluatePolicy() in src/praisonai-ts/src/mcp/security.ts invokes the configured credential validator only when AuthMethod is api-key or bearer. Basic and OAuth policies accept any non-empty Authorization header without calling auth.validate(), then return an authenticated result, allowing callers with invalid credentials to access MCP tools and resources protected by those policies. This issue is fixed in version 1.7.2.

Affected: npm: praisonai

## Summary

The published npm package `praisonai` exports an `MCPSecurity` helper described in source as:

```text MCP Security - Authentication, authorization, and rate limiting Provides security policies for MCP servers. ```

Its `AuthMethod` type advertises five authentication methods:

```ts export type AuthMethod = 'none' | 'api-key' | 'bearer' | 'basic' | 'oauth'; ```

The authentication-policy evaluator, however, only validates credentials for `api-key` and `bearer`:

```ts if (policy.auth.method === 'api-key' || policy.auth.method === 'bearer') { const valid = policy.auth.validate ? await policy.auth.validate(token) : this.validateApiKey(token);

if (!valid) { return { allowed: false, reason: 'Invalid credentials' }; } }

return { allowed: true, context: { authenticated: true } }; ```

For `basic` and `oauth`, any non-empty `Authorization` header skips the supplied `validate` callback and returns allowed. A local PoV configures `auth.validate` to always return `false`; invalid `api-key` and `bearer` credentials are rejected, while invalid `basic` and `oauth` credentials are accepted without calling the validator.

This is a protection-mechanism failure in the exported npm MCP security helper. It is distinct from the separate issue that the npm `MCPServer` HTTP transport does not enforce authentication by default.

## Technical Details

`SecurityPolicy.auth` accepts both a method and a validator:

```ts auth?: { method: AuthMethod;…