llama-stack-mcp-server

The HR Enterprise API (`hr-api`) implements security headers (`helmet`), rate limiting, and input validation (`express-validator`). However, its default `ALLOWED_ORIGINS` for CORS is `*`, which is highly insecure for production use with sensitive HR data. The Custom MCP Server uses a hardcoded default `HR_API_KEY='hr-api-default-key'` if not provided via environment variables, which is also a security concern for non-demo deployments. All data within the HR API is in-memory and non-persistent, making it unsuitable for real production use of sensitive data, though acceptable for a quickstart demo. There are no signs of 'eval', obfuscation, or overtly malicious patterns.